Systems, Methods, and Devices for Managing Coexistence of Multiple Transceiver Devices by Optimizing Component Layout

ABSTRACT

A camera assembly includes an enclosed housing having a rear surface, a front surface, and a periphery. The camera assembly also includes a lens module located within the housing and configured to receive light via the front surface, and a circuit board comprising communication circuitry located within the housing and configured to wireless communicate over a plurality of different communication protocols. The camera assembly further includes a first antenna arranged at a location on the circuit board, the first antenna configured for communication over a first one of the communication protocols, and a second antenna arranged at a location on the inner surface of the periphery, the second antenna configured for communication over a second one of the communication protocols.

RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 14/819,373, filed Aug. 5, 2015, entitled “Systems, Methods, andDevices for Managing Coexistence of Multiple Transceiver Devices byOptimizing Component Layout,” which itself claims priority to U.S.Provisional Application No. 62/175,393, filed Jun. 14, 2015, entitled“Systems, Methods, and Devices for Managing Coexistence of MultipleTransceiver Devices by Optimizing Component Layout,” both of which arehereby expressly incorporated by reference in their entirety.

This application is related to U.S. patent application Ser. No.14/616,302, filed Feb. 6, 2015, entitled “Systems and Methods forProcessing Coexisting Signals for Rapid Response to User Input,” U.S.patent application Ser. No. 13/656,189, filed Oct. 19, 2012, entitled“User-friendly, network connected learning thermostat and relatedsystems and methods,” and U.S. patent application Ser. No. 13/835,439,filed Mar. 15, 2013, entitled “Detector unit and sensing chambertherefor,” which are hereby incorporated by reference in their entirety.

TECHNICAL FIELD

This relates generally to computer technology, including but not limitedto methods and systems for managing coexistence of multiple transceiverdevices.

BACKGROUND

Devices in a smart home environment include a host of circuit componentsand interfaces for enabling communications with other systems, devices,and/or servers. For example, some smart devices include multiple radiosas components of a single integrated circuit collocated within a compactarea for receiving and transmitting signals to other devices and acrossnetworks. As a consequence of the close physical spacing of componentswithin smart devices, combined with close proximity to nearby conductivematerials and the fact that devices often share the same or closefrequency bands in operation, device components typically exhibit poorisolation from transmissions of one another. In addition to poorcommunications performance, sensitive device components are also at riskof damage when their input power thresholds are exceeded due to poorisolation.

SUMMARY

Accordingly, there is a need for methods, apparatuses, and systems formanaging coexistence of multiple transceivers in a device. By utilizingvarious component layout strategies within a device, using bypasscircuitry, and/or using various control signals for prioritizingtransmission access, the impact and harmful effects arising from poorlyisolated transceivers in a device are reduced.

In accordance with some implementations, a camera assembly includes anenclosed housing having a rear surface, a front surface, and aperiphery. Furthermore, the camera assembly includes a lens modulelocated within the housing and configured to receive light via the frontsurface, and communication circuitry located within the housing andconfigured to wireless communicate over a plurality of differentcommunication protocols. The camera assembly further includes a firstantenna arranged at a first location on an inner surface of theperiphery, the first antenna configured for communication over a firstone of the communication protocols, and a second antenna arranged at asecond location on the inner surface of the periphery, the secondlocation being different than the first location, the second antennaconfigured for communication over a second one of the communicationprotocols.

Another aspect includes a communications apparatus including a first andsecond transceiver, and a first and second antenna. The communicationsapparatus further includes a front end module (FEM) coupled between thefirst transceiver and the first antenna, the front end module includingan amplifier for amplifying signals received by the first antenna, and abypass line. The FEM is configured to couple the first antenna to thefirst transceiver via the bypass line when the second transceiver isactive and transmitting signals using the second antenna such that asignal received via the first antenna is not amplified by the amplifierprior to being passed to the first transceiver. Furthermore, the FEM isconfigured to couple the first antenna to the first transceiver via theamplifier when the second transceiver is not transmitting signals usingthe second antenna such that a signal received via the first antenna isamplified by the amplifier prior to being passed to the firsttransceiver.

In accordance with some implementations, a method for communicating viaa plurality of transceivers includes coupling a first transceiver of aplurality of transceivers of an electronic device to a first antenna viaan amplifier such that a signal received by the first antenna isamplified by the amplifier prior to being passed to the firsttransceiver, in accordance with detecting that a second transceiver ofthe plurality of transceivers is not transmitting signals via a secondantenna coupled to the second transceiver. The method further includescoupling the first transceiver to the first antenna via a bypass linesuch that a signal received by the first antenna is not amplified by theamplifier prior to being passed to the first transceiver, in accordancewith detecting that the second transceiver is transmitting signals viathe second antenna.

In accordance with some implementations, a communications apparatusincluding a first and second transceiver, and a first and secondantenna. The communications apparatus further includes a coupling means.The coupling means is configured to couple the first antenna to thefirst transceiver via the bypass line when the second transceiver isactive and transmitting signals using the second antenna such that asignal received via the first antenna is not amplified by the amplifierprior to being passed to the first transceiver. Furthermore, thecoupling means is configured to couple the first antenna to the firsttransceiver via the amplifier when the second transceiver is nottransmitting signals using the second antenna such that a signalreceived via the first antenna is amplified by the amplifier prior tobeing passed to the first transceiver

Another aspect includes a method for communicating via a plurality oftransceivers, the method performed at a camera device comprising aplurality of distinct transceivers configured for communication overrespective communication protocols, one or more processors, and memorystoring instructions for execution by the one or more processors. Themethod includes communicating using a first transceiver of the pluralityof transceivers, the first transceiver configured to transmit andreceive, over a first one of the communication protocols, signals forconfiguring the camera device. Furthermore, the method includescommunicating with one or more smart home devices using a secondtransceiver of the plurality of transceivers, the second transceiverconfigured to transmit and receive, over a second one of thecommunication protocols, signals comprising one or more of alerts,control signals and status information to and from the one or more smarthome devices. Furthermore, the method includes communicating using athird transceiver of the plurality of transceivers, the thirdtransceiver configured to transmit and receive, over a third one of thecommunication protocols, data corresponding to video captured by thecamera device.

In accordance with some implementations, a camera device includes afirst and second antenna, and a first, second, and third transceiver.The first transceiver is configured to transmit and receive, over afirst one of a plurality of distinct communication protocols, signalsfor configuring the camera device. Furthermore, the second transceiveris configured to transmit and receive, over a second one of theplurality of distinct communication protocols, signals comprising one ormore of alerts, control signals and status information to and from theone or more smart home devices. Moreover, the third transceiver isconfigured to transmit and receive, over a third one of the plurality ofdistinct communication protocols, data corresponding to video capturedby the camera device, wherein the second transceiver is coupled to thefirst antenna, and the first and third transceivers are coupled to thesecond antenna.

Antenna performance is generally characterized by metrics such asimpedance bandwidth, efficiency, directive gain, polarization, andradiation pattern. The same parameters are applicable for evaluatingboth transmitting and receiving operations, although the preferredvalues generally differ. Regarding impedance bandwidth, an antenna isgenerally a transducer between the characteristic impedance of a radiosystem (e.g., 50 ohms) and the impedance of free space. Thus, theantenna should comprise an acceptable impedance match over the frequencyband(s) of operation. The antenna's performance bandwidth is generallyproportional to the volume the antenna occupies, so very small antennasproduce inadequate bandwidth in some instances.

Antennas may be omni-directional or directional. However, evenomni-directional antennas generally have preferred directions where theradiated energy is greater than in one or more non-preferred directions.Efficient transfer of energy between two antennas includes optimizingthe antenna's respective radiation patterns as well as their respectiveenergy polarizations. However, many environmental factors affect anantenna's radiation pattern and/or polarization. For devices that have apreferred orientation, location, and/or position, the preferences may betaken into account to determine an optimal or sufficient radiationpattern.

Efficiency is another important performance parameter. Efficiency is ameasure of what portion of the power supplied to the antenna, includingany reflection loss, is actually radiated by the antenna. As discussedpreviously, tightly integrated antennas are susceptible to interferenceand/or loss making them less efficient. For example, nearby component,such as grounded conductors and dielectric materials (e.g., a typicalplastic housing), will constrain and/or absorb the near-fields of theantenna and cause significant losses. Energy loss may occur during bothreceive and transmit operations. However, the more efficient theantenna, the more it may interact with the local ground plane of thedevice.

Due to the interactions between an antenna and other components of adevice, determining what type of antenna to use for a particular deviceincludes considering characteristics of the entire device. Conductivecomponents of the device likely have the largest influence on anantenna, but non-conductive components also an effect on the antenna'sperformance. Antenna performance is also affected by electrical noisegenerated by the circuitry of the device and result in poor orintermittent performance; particularly if the circuitry is located nearthe antenna.

Wireless devices often have multiple transceivers operating in variousbands, such as Wi-Fi (optionally using Multiple Input Multiple Output),Bluetooth, ZigBee, GPS, etc. Each transceiver has an associated antenna,and signals and/or noise from one antenna creates interference withother antennas. Generally it is preferable to maximize the distancebetween the antennas so as to minimize the potential for interference.However, in some small devices, antennas must be placed near oneanother.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described implementations,reference should be made to the Description of Implementations below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1 is an example smart home environment, in accordance with someimplementations.

FIG. 2 is a block diagram illustrating an example network architecturethat includes a smart home network, in accordance with someimplementations.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations.

FIG. 4 illustrates an abstracted functional view of the extensibledevices and services platform of FIG. 3, with reference to a processingengine as well as devices of the smart home environment, in accordancewith some implementations.

FIG. 5 is a representative operating environment in which a hub deviceserver system interacts with client devices and hub devicescommunicatively coupled to local smart devices, in accordance with someimplementations.

FIG. 6 is a block diagram illustrating a representative hub device, inaccordance with some implementations.

FIG. 7 is a block diagram illustrating a representative hub serversystem, in accordance with some implementations.

FIG. 8 is a block diagram illustrating a representative client deviceassociated with a user account, in accordance with some implementations.

FIG. 9 is a block diagram illustrating a representative smart device, inaccordance with some implementations.

FIG. 10 is a block diagram illustrating a representative smart homeprovider server system, in accordance with some implementations.

FIGS. 11A-11M illustrate various assembly views of a camera device 118,in accordance with some implementations.

FIGS. 12A-12C illustrate various component views of a thermostat, inaccordance with some implementations.

FIGS. 13A-13D illustrate various component views of a hazard detector,in accordance with some implementations.

FIG. 14 illustrates a block diagram of a communications module of asmart device utilizing a bypass coexistence technique, in accordancewith some implementations.

FIGS. 15A-15L illustrate a coexistence scheme for a smart device havingmultiple radios in smart home environment, in accordance with someimplementations.

FIG. 16 shows an illustrative co-existence circuit for managingoperations of three communications circuits, in accordance with someimplementations.

FIGS. 17A-17B show priority cases for Wi-Fi circuitry, in accordancewith some implementations.

FIGS. 18A-D shows different illustrative 6LoWPAN priority use cases, inaccordance with some implementations.

FIGS. 19A-19B show illustrative timing diagrams where Wi-Fi circuitry isOFF, in accordance with some implementations.

FIG. 20 shows an illustrative timing diagram showing how the BLEcircuitry attempts to communicate with a personal device during the idleportion of a wake packet being transmitted by 6LoWPAN circuitry during aNCCA period, in accordance with some implementations.

FIG. 21 shows illustrative timing diagrams of exemplary BLE advertise,connect, and data transfer activity during BLE transmissions, inaccordance with some implementations.

FIG. 22 is a flow diagram illustrating a method of coexistence usingbypass circuitry, in accordance with some implementations.

FIGS. 23A-23F are flow diagrams illustrating methods of using controlsignals in a coexistence scheme, in accordance with someimplementations.

FIGS. 24A-24D illustrate various types of antennas for use with thevarious devices disclosed herein.

FIGS. 25A-25F illustrate various assembly views of a camera device, inaccordance with some implementations.

FIGS. 26A-26J illustrate various assembly views of a camera device, inaccordance with some implementations.

FIGS. 27A-27I illustrate various assembly views of a camera device, inaccordance with some implementations.

FIGS. 28A-28N illustrate various assembly views of a camera device, inaccordance with some implementations.

FIGS. 29A-29I illustrate various assembly views of a camera device, inaccordance with some implementations.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DESCRIPTION OF IMPLEMENTATIONS

Reference will now be made in detail to implementations, examples ofwhich are illustrated in the accompanying drawings. In the followingdetailed description, numerous specific details are set forth in orderto provide a thorough understanding of the various describedimplementations. However, it will be apparent to one of ordinary skillin the art that the various described implementations may be practicedwithout these specific details. In other instances, well-known methods,procedures, components, circuits, and networks have not been describedin detail so as not to unnecessarily obscure aspects of theimplementations.

FIG. 1 is an example smart home environment 100 in accordance with someimplementations. Smart home environment 100 includes a structure 150(e.g., a house, office building, garage, or mobile home) with variousintegrated devices. It will be appreciated that devices may also beintegrated into a smart home environment 100 that does not include anentire structure 150, such as an apartment, condominium, or officespace. Further, the smart home environment 100 may control and/or becoupled to devices outside of the actual structure 150. Indeed, severaldevices in the smart home environment 100 need not be physically withinthe structure 150. For example, a device controlling a pool heater 114or irrigation system 116 may be located outside of the structure 150.

The depicted structure 150 includes a plurality of rooms 152, separatedat least partly from each other via walls 154. The walls 154 may includeinterior walls or exterior walls. Each room may further include a floor156 and a ceiling 158. Devices may be mounted on, integrated with and/orsupported by a wall 154, floor 156 or ceiling 158.

In some implementations, the integrated devices of the smart homeenvironment 100 include intelligent, multi-sensing, network-connecteddevices that integrate seamlessly with each other in a smart homenetwork (e.g., 202 FIG. 2) and/or with a central server or acloud-computing system to provide a variety of useful smart homefunctions. The smart home environment 100 may include one or moreintelligent, multi-sensing, network-connected thermostats 102(hereinafter referred to as “smart thermostats 102”), one or moreintelligent, network-connected, multi-sensing hazard detection units 104(hereinafter referred to as “smart hazard detectors 104”), one or moreintelligent, multi-sensing, network-connected entryway interface devices106 and 120 (hereinafter referred to as “smart doorbells 106” and “smartdoor locks 120”), and one or more intelligent, multi-sensing,network-connected alarm systems 122 (hereinafter referred to as “smartalarm systems 122”).

In some implementations, the one or more smart thermostats 102 detectambient climate characteristics (e.g., temperature and/or humidity) andcontrol a HVAC system 103 accordingly. For example, a respective smartthermostat 102 includes an ambient temperature sensor.

The one or more smart hazard detectors 104 may include thermal radiationsensors directed at respective heat sources (e.g., a stove, oven, otherappliances, a fireplace, etc.). For example, a smart hazard detector 104in a kitchen 153 includes a thermal radiation sensor directed at astove/oven 112. A thermal radiation sensor may determine the temperatureof the respective heat source (or a portion thereof) at which it isdirected and may provide corresponding blackbody radiation data asoutput.

The smart doorbell 106 and/or the smart door lock 120 may detect aperson's approach to or departure from a location (e.g., an outer door),control doorbell/door locking functionality (e.g., receive user inputsfrom a portable electronic device 166-1 to actuate bolt of the smartdoor lock 120), announce a person's approach or departure via audio orvisual means, and/or control settings on a security system (e.g., toactivate or deactivate the security system when occupants go and come).

The smart alarm system 122 may detect the presence of an individualwithin close proximity (e.g., using built-in IR sensors), sound an alarm(e.g., through a built-in speaker, or by sending commands to one or moreexternal speakers), and send notifications to entities or userswithin/outside of the smart home network 100. In some implementations,the smart alarm system 122 also includes one or more input devices orsensors (e.g., keypad, biometric scanner, NFC transceiver, microphone)for verifying the identity of a user, and one or more output devices(e.g., display, speaker). In some implementations, the smart alarmsystem 122 may also be set to an “armed” mode, such that detection of atrigger condition or event causes the alarm to be sounded unless adisarming action is performed.

In some implementations, the smart home environment 100 includes one ormore intelligent, multi-sensing, network-connected wall switches 108(hereinafter referred to as “smart wall switches 108”), along with oneor more intelligent, multi-sensing, network-connected wall pluginterfaces 110 (hereinafter referred to as “smart wall plugs 110”). Thesmart wall switches 108 may detect ambient lighting conditions, detectroom-occupancy states, and control a power and/or dim state of one ormore lights. In some instances, smart wall switches 108 may also controla power state or speed of a fan, such as a ceiling fan. The smart wallplugs 110 may detect occupancy of a room or enclosure and control supplyof power to one or more wall plugs (e.g., such that power is notsupplied to the plug if nobody is at home).

In some implementations, the smart home environment 100 of FIG. 1includes a plurality of intelligent, multi-sensing, network-connectedappliances 112 (hereinafter referred to as “smart appliances 112”), suchas refrigerators, stoves, ovens, televisions, washers, dryers, lights,stereos, intercom systems, garage-door openers, floor fans, ceilingfans, wall air conditioners, pool heaters, irrigation systems, securitysystems, space heaters, window AC units, motorized duct vents, and soforth. In some implementations, when plugged in, an appliance mayannounce itself to the smart home network, such as by indicating whattype of appliance it is, and it may automatically integrate with thecontrols of the smart home. Such communication by the appliance to thesmart home may be facilitated by either a wired or wirelesscommunication protocol. The smart home may also include a variety ofnon-communicating legacy appliances 140, such as old conventionalwasher/dryers, refrigerators, and the like, which may be controlled bysmart wall plugs 110. The smart home environment 100 may further includea variety of partially communicating legacy appliances 142, such asinfrared (“IR”) controlled wall air conditioners or other IR-controlleddevices, which may be controlled by IR signals provided by the smarthazard detectors 104 or the smart wall switches 108.

In some implementations, the smart home environment 100 includes one ormore network-connected cameras 118 that are configured to provide videomonitoring and security in the smart home environment 100. The cameras118 may be used to determine occupancy of the structure 150 and/orparticular rooms 152 in the structure 150, and thus may act as occupancysensors. For example, video captured by the cameras 118 may be processedto identify the presence of an occupant in the structure 150 (e.g., in aparticular room 152). Specific individuals may be identified based, forexample, on their appearance (e.g., height, face) and/or movement (e.g.,their walk/gait). Cameras 118 may additionally include one or moresensors (e.g., IR sensors, motion detectors), input devices (e.g.,microphone for capturing audio), and output devices (e.g., speaker foroutputting audio).

The smart home environment 100 may additionally or alternatively includeone or more other occupancy sensors (e.g., the smart doorbell 106, smartdoor locks 120, touch screens, IR sensors, microphones, ambient lightsensors, motion detectors, smart nightlights 170, etc.). In someimplementations, the smart home environment 100 includes radio-frequencyidentification (RFID) readers (e.g., in each room 152 or a portionthereof) that determine occupancy based on RFID tags located on orembedded in occupants. For example, RFID readers may be integrated intothe smart hazard detectors 104.

The smart home environment 100 may also include communication withdevices outside of the physical home but within a proximate geographicalrange of the home. For example, the smart home environment 100 mayinclude a pool heater monitor 114 that communicates a current pooltemperature to other devices within the smart home environment 100and/or receives commands for controlling the pool temperature.Similarly, the smart home environment 100 may include an irrigationmonitor 116 that communicates information regarding irrigation systemswithin the smart home environment 100 and/or receives controlinformation for controlling such irrigation systems.

By virtue of network connectivity, one or more of the smart home devicesof FIG. 1 may further allow a user to interact with the device even ifthe user is not proximate to the device. For example, a user maycommunicate with a device using a computer (e.g., a desktop computer,laptop computer, or tablet) or other portable electronic device 166(e.g., a mobile phone, such as a smart phone). A webpage or applicationmay be configured to receive communications from the user and controlthe device based on the communications and/or to present informationabout the device's operation to the user. For example, the user may viewa current set point temperature for a device (e.g., a stove) and adjustit using a computer. The user may be in the structure during this remotecommunication or outside the structure.

As discussed above, users may control smart devices in the smart homeenvironment 100 using a network-connected computer or portableelectronic device 166. In some examples, some or all of the occupants(e.g., individuals who live in the home) may register their device 166with the smart home environment 100. Such registration may be made at acentral server to authenticate the occupant and/or the device as beingassociated with the home and to give permission to the occupant to usethe device to control the smart devices in the home. An occupant may usetheir registered device 166 to remotely control the smart devices of thehome, such as when the occupant is at work or on vacation. The occupantmay also use their registered device to control the smart devices whenthe occupant is actually located inside the home, such as when theoccupant is sitting on a couch inside the home. It should be appreciatedthat instead of or in addition to registering devices 166, the smarthome environment 100 may make inferences about which individuals live inthe home and are therefore occupants and which devices 166 areassociated with those individuals. As such, the smart home environmentmay “learn” who is an occupant and permit the devices 166 associatedwith those individuals to control the smart devices of the home.

In some implementations, in addition to containing processing andsensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116,118, 120, and/or 122 (collectively referred to as “the smart devices”)are capable of data communications and information sharing with othersmart devices, a central server or cloud-computing system, and/or otherdevices that are network-connected. Data communications may be carriedout using any of a variety of custom or standard wireless protocols(e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, BluetoothSmart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety ofcustom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), orany other suitable communication protocol, including communicationprotocols not yet developed as of the filing date of this document.

In some implementations, the smart devices serve as wireless or wiredrepeaters. In some implementations, a first one of the smart devicescommunicates with a second one of the smart devices via a wirelessrouter. The smart devices may further communicate with each other via aconnection (e.g., network interface 160) to a network, such as theInternet 162. Through the Internet 162, the smart devices maycommunicate with a smart home provider server system 164 (also called acentral server system and/or a cloud-computing system herein). The smarthome provider server system 164 may be associated with a manufacturer,support entity, or service provider associated with the smart device(s).In some implementations, a user is able to contact customer supportusing a smart device itself rather than needing to use othercommunication means, such as a telephone or Internet-connected computer.In some implementations, software updates are automatically sent fromthe smart home provider server system 164 to smart devices (e.g., whenavailable, when purchased, or at routine intervals).

In some implementations, the network interface 160 includes aconventional network device (e.g., a router), and the smart homeenvironment 100 of FIG. 1 includes a hub device 180 that iscommunicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the above intelligent, multi-sensing,network-connected devices (e.g., smart devices of the smart homeenvironment 100). Each of these smart devices optionally communicateswith the hub device 180 using one or more radio communication networksavailable at least in the smart home environment 100 (e.g., ZigBee,Z-Wave, Insteon, Bluetooth, Wi-Fi and other radio communicationnetworks). In some implementations, the hub device 180 and devicescoupled with/to the hub device can be controlled and/or interacted withvia an application running on a smart phone, household controller,laptop, tablet computer, game console or similar electronic device. Insome implementations, a user of such controller application can viewstatus of the hub device or coupled smart devices, configure the hubdevice to interoperate with smart devices newly introduced to the homenetwork, commission new smart devices, and adjust or view settings ofconnected smart devices, etc. In some implementations the hub deviceextends capabilities of low capability smart device to matchcapabilities of the highly capable smart devices of the same type,integrates functionality of multiple different device types—even acrossdifferent communication protocols, and is configured to streamlineadding of new devices and commissioning of the hub device.

It is to be appreciated that “smart home environments” may refer tosmart environments for homes such as a single-family house, but thescope of the present teachings is not so limited. The present teachingsare also applicable, without limitation, to duplexes, townhomes,multi-unit apartment buildings, hotels, retail stores, office buildings,industrial buildings, and more generally any living space or work space.

It is also to be appreciated that while the terms user, customer,installer, homeowner, occupant, guest, tenant, landlord, repair person,and the like may be used to refer to the person or persons acting in thecontext of some particularly situations described herein, thesereferences do not limit the scope of the present teachings with respectto the person or persons who are performing such actions. Thus, forexample, the terms user, customer, purchaser, installer, subscriber, andhomeowner may often refer to the same person in the case of asingle-family residential dwelling, because the head of the household isoften the person who makes the purchasing decision, buys the unit, andinstalls and configures the unit, and is also one of the users of theunit. However, in other scenarios, such as a landlord-tenantenvironment, the customer may be the landlord with respect to purchasingthe unit, the installer may be a local apartment supervisor, a firstuser may be the tenant, and a second user may again be the landlord withrespect to remote control functionality. Importantly, while the identityof the person performing the action may be germane to a particularadvantage provided by one or more of the implementations, such identityshould not be construed in the descriptions that follow as necessarilylimiting the scope of the present teachings to those particularindividuals having those particular identities.

FIG. 2 is a block diagram illustrating an example network architecture200 that includes a smart home network 202 in accordance with someimplementations. In some implementations, the smart devices 204 in thesmart home environment 100 (e.g., devices 102, 104, 106, 108, 110, 112,114, 116, 118, 120, and/or 122) combine with the hub device 180 tocreate a mesh network in smart home network 202. In someimplementations, one or more smart devices 204 in the smart home network202 operate as a smart home controller. Additionally and/oralternatively, hub device 180 operates as the smart home controller. Insome implementations, a smart home controller has more computing powerthan other smart devices. In some implementations, a smart homecontroller processes inputs (e.g., from smart devices 204, electronicdevice 166, and/or smart home provider server system 164) and sendscommands (e.g., to smart devices 204 in the smart home network 202) tocontrol operation of the smart home environment 100. In someimplementations, some of the smart devices 204 in the smart home network202 (e.g., in the mesh network) are “spokesman” nodes (e.g., 204-1) andothers are “low-powered” nodes (e.g., 204-9). Some of the smart devicesin the smart home environment 100 are battery powered, while others havea regular and reliable power source, such as by connecting to wiring(e.g., to 120V line voltage wires) behind the walls 154 of the smarthome environment. The smart devices that have a regular and reliablepower source are referred to as “spokesman” nodes. These nodes aretypically equipped with the capability of using a wireless protocol tofacilitate bidirectional communication with a variety of other devicesin the smart home environment 100, as well as with the smart homeprovider server system 164. In some implementations, one or more“spokesman” nodes operate as a smart home controller. On the other hand,the devices that are battery powered are the “low-power” nodes. Thesenodes tend to be smaller than spokesman nodes and typically onlycommunicate using wireless protocols that require very little power,such as Zigbee, 6LoWPAN, etc.

In some implementations, some low-power nodes are incapable ofbidirectional communication. These low-power nodes send messages, butthey are unable to “listen”. Thus, other devices in the smart homeenvironment 100, such as the spokesman nodes, cannot send information tothese low-power nodes.

In some implementations, some low-power nodes are capable of only alimited bidirectional communication. For example, other devices are ableto communicate with the low-power nodes only during a certain timeperiod.

As described, in some implementations, the smart devices serve aslow-power and spokesman nodes to create a mesh network in the smart homeenvironment 100. In some implementations, individual low-power nodes inthe smart home environment regularly send out messages regarding whatthey are sensing, and the other low-powered nodes in the smart homeenvironment—in addition to sending out their own messages—forward themessages, thereby causing the messages to travel from node to node(i.e., device to device) throughout the smart home network 202. In someimplementations, the spokesman nodes in the smart home network 202,which are able to communicate using a relatively high-powercommunication protocol, such as IEEE 802.11, are able to switch to arelatively low-power communication protocol, such as IEEE 802.15.4, toreceive these messages, translate the messages to other communicationprotocols, and send the translated messages to other spokesman nodesand/or the smart home provider server system 164 (using, e.g., therelatively high-power communication protocol). Thus, the low-powerednodes using low-power communication protocols are able to send and/orreceive messages across the entire smart home network 202, as well asover the Internet 162 to the smart home provider server system 164. Insome implementations, the mesh network enables the smart home providerserver system 164 to regularly receive data from most or all of thesmart devices in the home, make inferences based on the data, facilitatestate synchronization across devices within and outside of the smarthome network 202, and send commands to one or more of the smart devicesto perform tasks in the smart home environment.

As described, the spokesman nodes and some of the low-powered nodes arecapable of “listening.” Accordingly, users, other devices, and/or thesmart home provider server system 164 may communicate control commandsto the low-powered nodes. For example, a user may use the electronicdevice 166 (e.g., a smart phone) to send commands over the Internet tothe smart home provider server system 164, which then relays thecommands to one or more spokesman nodes in the smart home network 202.The spokesman nodes may use a low-power protocol to communicate thecommands to the low-power nodes throughout the smart home network 202,as well as to other spokesman nodes that did not receive the commandsdirectly from the smart home provider server system 164.

In some implementations, a smart nightlight 170 (FIG. 1), which is anexample of a smart device 204, is a low-power node. In addition tohousing a light source, the smart nightlight 170 houses an occupancysensor, such as an ultrasonic or passive IR sensor, and an ambient lightsensor, such as a photo resistor or a single-pixel sensor that measureslight in the room. In some implementations, the smart nightlight 170 isconfigured to activate the light source when its ambient light sensordetects that the room is dark and when its occupancy sensor detects thatsomeone is in the room. In other implementations, the smart nightlight170 is simply configured to activate the light source when its ambientlight sensor detects that the room is dark. Further, in someimplementations, the smart nightlight 170 includes a low-power wirelesscommunication chip (e.g., a ZigBee chip) that regularly sends outmessages regarding the occupancy of the room and the amount of light inthe room, including instantaneous messages coincident with the occupancysensor detecting the presence of a person in the room. As mentionedabove, these messages may be sent wirelessly (e.g., using the meshnetwork) from node to node (i.e., smart device to smart device) withinthe smart home network 202 as well as over the Internet 162 to the smarthome provider server system 164.

Other examples of low-power nodes include battery-operated versions ofthe smart hazard detectors 104. These smart hazard detectors 104 areoften located in an area without access to constant and reliable powerand may include any number and type of sensors, such as smoke/fire/heatsensors (e.g., thermal radiation sensors), carbon monoxide/dioxidesensors, occupancy/motion sensors, ambient light sensors, ambienttemperature sensors, humidity sensors, and the like. Furthermore, smarthazard detectors 104 may send messages that correspond to each of therespective sensors to the other devices and/or the smart home providerserver system 164, such as by using the mesh network as described above.

Examples of spokesman nodes include smart doorbells 106, smartthermostats 102, smart wall switches 108, and smart wall plugs 110.These devices are often located near and connected to a reliable powersource, and therefore may include more power-consuming components, suchas one or more communication chips capable of bidirectionalcommunication in a variety of protocols.

In some implementations, the smart home environment 100 includes servicerobots 168 (FIG. 1) that are configured to carry out, in an autonomousmanner, any of a variety of household tasks.

As explained above with reference to FIG. 1, in some implementations,the smart home environment 100 of FIG. 1 includes a hub device 180 thatis communicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the smart devices using a radio communicationnetwork that is available at least in the smart home environment 100.Communication protocols used by the radio communication network include,but are not limited to, ZigBee, Z-Wave, Insteon, EuOcean, Thread, OSIAN,Bluetooth Low Energy and the like. In some implementations, the hubdevice 180 not only converts the data received from each smart device tomeet the data format requirements of the network interface 160 or thenetwork(s) 162, but also converts information received from the networkinterface 160 or the network(s) 162 to meet the data format requirementsof the respective communication protocol associated with a targetedsmart device. In some implementations, in addition to data formatconversion, the hub device 180 further processes the data received fromthe smart devices or information received from the network interface 160or the network(s) 162 preliminary. For example, the hub device 180 canintegrate inputs from multiple sensors/connected devices (includingsensors/devices of the same and/or different types), perform higherlevel processing on those inputs—e.g., to assess the overall environmentand coordinate operation among the different sensors/devices—and/orprovide instructions to the different devices based on the collection ofinputs and programmed processing. It is also noted that in someimplementations, the network interface 160 and the hub device 180 areintegrated to one network device. Functionality described herein isrepresentative of particular implementations of smart devices, controlapplication(s) running on representative electronic device(s) (such as asmart phone), hub device(s) 180, and server(s) coupled to hub device(s)via the Internet or other Wide Area Network. All or a portion of thisfunctionality and associated operations can be performed by any elementsof the described system—for example, all or a portion of thefunctionality described herein as being performed by an implementationof the hub device can be performed, in different system implementations,in whole or in part on the server, one or more connected smart devicesand/or the control application, or different combinations thereof.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations. The extensibledevices and services platform 300 includes smart home provider serversystem 164. Each of the intelligent, network-connected devices describedwith reference to FIG. 1 (e.g., 102, 104, 106, 108, 110, 112, 114, 116and 118, identified simply as “devices” in FIGS. 2-4) may communicatewith the smart home provider server system 164. For example, aconnection to the Internet 162 may be established either directly (forexample, using 3G/4G connectivity to a wireless carrier), or through anetwork interface 160 (e.g., a router, switch, gateway, hub device, oran intelligent, dedicated whole-home controller node), or through anycombination thereof.

In some implementations, the devices and services platform 300communicates with and collects data from the smart devices of the smarthome environment 100. In addition, in some implementations, the devicesand services platform 300 communicates with and collects data from aplurality of smart home environments across the world. For example, thesmart home provider server system 164 collects home data 302 from thedevices of one or more smart home environments 100, where the devicesmay routinely transmit home data or may transmit home data in specificinstances (e.g., when a device queries the home data 302). Examplecollected home data 302 includes, without limitation, power consumptiondata, blackbody radiation data, occupancy data, HVAC settings and usagedata, carbon monoxide levels data, carbon dioxide levels data, volatileorganic compounds levels data, sleeping schedule data, cooking scheduledata, inside and outside temperature humidity data, televisionviewership data, inside and outside noise level data, pressure data,video data, etc.

In some implementations, the smart home provider server system 164provides one or more services 304 to smart homes and/or third parties.Example services 304 include, without limitation, software updates,customer support, sensor data collection/logging, remote access, remoteor distributed control, and/or use suggestions (e.g., based on collectedhome data 302) to improve performance, reduce utility cost, increasesafety, etc. In some implementations, data associated with the services304 is stored at the smart home provider server system 164, and thesmart home provider server system 164 retrieves and transmits the dataat appropriate times (e.g., at regular intervals, upon receiving arequest from a user, etc.).

In some implementations, the extensible devices and services platform300 includes a processing engine 306, which may be concentrated at asingle server or distributed among several different computing entitieswithout limitation. In some implementations, the processing engine 306includes engines configured to receive data from the devices of smarthome environments 100 (e.g., via the Internet 162 and/or a networkinterface 160), to index the data, to analyze the data and/or togenerate statistics based on the analysis or as part of the analysis. Insome implementations, the analyzed data is stored as derived home data308.

Results of the analysis or statistics may thereafter be transmitted backto the device that provided home data used to derive the results, toother devices, to a server providing a webpage to a user of the device,or to other non-smart device entities. In some implementations, usagestatistics, usage statistics relative to use of other devices, usagepatterns, and/or statistics summarizing sensor readings are generated bythe processing engine 306 and transmitted. The results or statistics maybe provided via the Internet 162. In this manner, the processing engine306 may be configured and programmed to derive a variety of usefulinformation from the home data 302. A single server may include one ormore processing engines.

The derived home data 308 may be used at different granularities for avariety of useful purposes, ranging from explicit programmed control ofthe devices on a per-home, per-neighborhood, or per-region basis (forexample, demand-response programs for electrical utilities), to thegeneration of inferential abstractions that may assist on a per-homebasis (for example, an inference may be drawn that the homeowner hasleft for vacation and so security detection equipment may be put onheightened sensitivity), to the generation of statistics and associatedinferential abstractions that may be used for government or charitablepurposes. For example, processing engine 306 may generate statisticsabout device usage across a population of devices and send thestatistics to device users, service providers or other entities (e.g.,entities that have requested the statistics and/or entities that haveprovided monetary compensation for the statistics).

In some implementations, to encourage innovation and research and toincrease products and services available to users, the devices andservices platform 300 exposes a range of application programminginterfaces (APIs) 310 to third parties, such as charities 314,governmental entities 316 (e.g., the Food and Drug Administration or theEnvironmental Protection Agency), academic institutions 318 (e.g.,university researchers), businesses 320 (e.g., providing devicewarranties or service to related equipment, targeting advertisementsbased on home data), utility companies 324, and other third parties. TheAPIs 310 are coupled to and permit third-party systems to communicatewith the smart home provider server system 164, including the services304, the processing engine 306, the home data 302, and the derived homedata 308. In some implementations, the APIs 310 allow applicationsexecuted by the third parties to initiate specific data processing tasksthat are executed by the smart home provider server system 164, as wellas to receive dynamic updates to the home data 302 and the derived homedata 308.

For example, third parties may develop programs and/or applications(e.g., web applications or mobile applications) that integrate with thesmart home provider server system 164 to provide services andinformation to users. Such programs and applications may be, forexample, designed to help users reduce energy consumption, topreemptively service faulty equipment, to prepare for high servicedemands, to track past service performance, etc., and/or to performother beneficial functions or tasks.

FIG. 4 illustrates an abstracted functional view 400 of the extensibledevices and services platform 300 of FIG. 3, with reference to aprocessing engine 306 as well as devices of the smart home environment,in accordance with some implementations. Even though devices situated insmart home environments will have a wide variety of different individualcapabilities and limitations, the devices may be thought of as sharingcommon characteristics in that each device is a data consumer 402 (DC),a data source 404 (DS), a services consumer 406 (SC), and a servicessource 408 (SS). Advantageously, in addition to providing controlinformation used by the devices to achieve their local and immediateobjectives, the extensible devices and services platform 300 may also beconfigured to use the large amount of data that is generated by thesedevices. In addition to enhancing or optimizing the actual operation ofthe devices themselves with respect to their immediate functions, theextensible devices and services platform 300 may be directed to“repurpose” that data in a variety of automated, extensible, flexible,and/or scalable ways to achieve a variety of useful objectives. Theseobjectives may be predefined or adaptively identified based on, e.g.,usage patterns, device efficiency, and/or user input (e.g., requestingspecific functionality).

FIG. 4 shows processing engine 306 as including a number of processingparadigms 410. In some implementations, processing engine 306 includes amanaged services paradigm 410 a that monitors and manages primary orsecondary device functions. The device functions may include ensuringproper operation of a device given user inputs, estimating that (e.g.,and responding to an instance in which) an intruder is or is attemptingto be in a dwelling, detecting a failure of equipment coupled to thedevice (e.g., a light bulb having burned out), implementing or otherwiseresponding to energy demand response events, providing a heat-sourcealert, and/or alerting a user of a current or predicted future event orcharacteristic. In some implementations, processing engine 306 includesan advertising/communication paradigm 410 b that estimatescharacteristics (e.g., demographic information), desires and/or productsof interest of a user based on device usage. Services, promotions,products or upgrades may then be offered or automatically provided tothe user. In some implementations, processing engine 306 includes asocial paradigm 410 c that uses information from a social network,provides information to a social network (for example, based on deviceusage), and/or processes data associated with user and/or deviceinteractions with the social network platform. For example, a user'sstatus as reported to their trusted contacts on the social network maybe updated to indicate when the user is home based on light detection,security system inactivation or device usage detectors. As anotherexample, a user may be able to share device-usage statistics with otherusers. In yet another example, a user may share HVAC settings thatresult in low power bills and other users may download the HVAC settingsto their smart thermostat 102 to reduce their power bills.

In some implementations, processing engine 306 includes achallenges/rules/compliance/rewards paradigm 410 d that informs a userof challenges, competitions, rules, compliance regulations and/orrewards and/or that uses operation data to determine whether a challengehas been met, a rule or regulation has been complied with and/or areward has been earned. The challenges, rules, and/or regulations mayrelate to efforts to conserve energy, to live safely (e.g., reducing theoccurrence of heat-source alerts) (e.g., reducing exposure to toxins orcarcinogens), to conserve money and/or equipment life, to improvehealth, etc. For example, one challenge may involve participants turningdown their thermostat by one degree for one week. Those participantsthat successfully complete the challenge are rewarded, such as withcoupons, virtual currency, status, etc. Regarding compliance, an exampleinvolves a rental-property owner making a rule that no renters arepermitted to access certain owner's rooms. The devices in the roomhaving occupancy sensors may send updates to the owner when the room isaccessed.

In some implementations, processing engine 306 integrates or otherwiseuses extrinsic information 412 from extrinsic sources to improve thefunctioning of one or more processing paradigms. Extrinsic information412 may be used to interpret data received from a device, to determine acharacteristic of the environment near the device (e.g., outside astructure that the device is enclosed in), to determine services orproducts available to the user, to identify a social network orsocial-network information, to determine contact information of entities(e.g., public-service entities such as an emergency-response team, thepolice or a hospital) near the device, to identify statistical orenvironmental conditions, trends or other information associated with ahome or neighborhood, and so forth.

FIG. 5 illustrates a representative operating environment 500 in which ahub device server system 508 provides data processing for monitoring andfacilitating review of motion events in video streams captured by videocameras 118. As shown in FIG. 5, the hub device server system 508receives video data from video sources 522 (including cameras 118)located at various physical locations (e.g., inside homes, restaurants,stores, streets, parking lots, and/or the smart home environments 100 ofFIG. 1). Each video source 522 may be bound to one or more revieweraccounts, and the hub device server system 508 provides video monitoringdata for the video source 522 to client devices 504 associated with thereviewer accounts. For example, the portable electronic device 166 is anexample of the client device 504.

In some implementations, the smart home provider server system 164 or acomponent thereof serves as the hub device server system 508. In someimplementations, the hub device server system 508 is a dedicated videoprocessing server that provides video processing services to videosources and client devices 504 independent of other services provided bythe hub device server system 508.

In some implementations, each of the video sources 522 includes one ormore video cameras 118 that capture video and send the captured video tothe hub device server system 508 substantially in real-time. In someimplementations, each of the video sources 522 optionally includes acontroller device (not shown) that serves as an intermediary between theone or more cameras 118 and the hub device server system 508. Thecontroller device receives the video data from the one or more cameras118, optionally, performs some preliminary processing on the video data,and sends the video data to the hub device server system 508 on behalfof the one or more cameras 118 substantially in real-time. In someimplementations, each camera has its own on-board processingcapabilities to perform some preliminary processing on the capturedvideo data before sending the processed video data (along with metadataobtained through the preliminary processing) to the controller deviceand/or the hub device server system 508.

As shown in FIG. 5, in accordance with some implementations, each of theclient devices 504 includes a client-side module 502. The client-sidemodule 502 communicates with a server-side module 506 executed on thehub device server system 508 through the one or more networks 162. Theclient-side module 502 provides client-side functionalities for theevent monitoring and review processing and communications with theserver-side module 506. The server-side module 506 provides server-sidefunctionalities for event monitoring and review processing for anynumber of client-side modules 502 each residing on a respective clientdevice 504. The server-side module 506 also provides server-sidefunctionalities for video processing and camera control for any numberof the video sources 522, including any number of control devices andthe cameras 118.

In some implementations, the server-side module 506 includes one or moreprocessors 512, a video storage database 514, device and accountdatabases 516, an I/O interface to one or more client devices 518, andan I/O interface to one or more video sources 520. The I/O interface toone or more clients 518 facilitates the client-facing input and outputprocessing for the server-side module 506. The databases 516 store aplurality of profiles for reviewer accounts registered with the videoprocessing server, where a respective user profile includes accountcredentials for a respective reviewer account, and one or more videosources linked to the respective reviewer account. The I/O interface toone or more video sources 520 facilitates communications with one ormore video sources 522 (e.g., groups of one or more cameras 118 andassociated controller devices). The video storage database 514 storesraw video data received from the video sources 522, as well as varioustypes of metadata, such as motion events, event categories, eventcategory models, event filters, and event masks, for use in dataprocessing for event monitoring and review for each reviewer account.

Examples of a representative client device 504 include, but are notlimited to, a handheld computer, a wearable computing device, a personaldigital assistant (PDA), a tablet computer, a laptop computer, a desktopcomputer, a cellular telephone, a smart phone, an enhanced generalpacket radio service (EGPRS) mobile phone, a media player, a navigationdevice, a game console, a television, a remote control, a point-of-sale(POS) terminal, vehicle-mounted computer, an ebook reader, or acombination of any two or more of these data processing devices or otherdata processing devices.

Examples of the one or more networks 162 include local area networks(LAN) and wide area networks (WAN) such as the Internet. The one or morenetworks 162 are, optionally, implemented using any known networkprotocol, including various wired or wireless protocols, such asEthernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution(LTE), Global System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), code division multiple access (CDMA), time divisionmultiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol(VoIP), Wi-MAX, or any other suitable communication protocol.

In some implementations, the hub device server system 508 is implementedon one or more standalone data processing apparatuses or a distributednetwork of computers. In some implementations, the hub device serversystem 508 also employs various virtual devices and/or services of thirdparty service providers (e.g., third-party cloud service providers) toprovide the underlying computing resources and/or infrastructureresources of the hub device server system 508. In some implementations,the hub device server system 508 includes, but is not limited to, ahandheld computer, a tablet computer, a laptop computer, a desktopcomputer, or a combination of any two or more of these data processingdevices or other data processing devices.

The server-client environment 500 shown in FIG. 1 includes both aclient-side portion (e.g., the client-side module 502) and a server-sideportion (e.g., the server-side module 506). The division offunctionalities between the client and server portions of operatingenvironment 500 can vary in different implementations. Similarly, thedivision of functionalities between the video source 522 and the hubdevice server system 508 can vary in different implementations. Forexample, in some implementations, client-side module 502 is athin-client that provides only user-facing input and output processingfunctions, and delegates all other data processing functionalities to abackend server (e.g., the hub device server system 508). Similarly, insome implementations, a respective one of the video sources 522 is asimple video capturing device that continuously captures and streamsvideo data to the hub device server system 508 without no or limitedlocal preliminary processing on the video data. Although many aspects ofthe present technology are described from the perspective of the hubdevice server system 508, the corresponding actions performed by theclient device 504 and/or the video sources 522 would be apparent to onesskilled in the art without any creative efforts. Similarly, some aspectsof the present technology may be described from the perspective of theclient device or the video source, and the corresponding actionsperformed by the video server would be apparent to ones skilled in theart without any creative efforts. Furthermore, some aspects of thepresent technology may be performed by the hub device server system 508,the client device 504, and the video sources 522 cooperatively.

It should be understood that operating environment 500 that involves thehub device server system 508, the video sources 522 and the videocameras 118 is merely an example. Many aspects of operating environment500 are generally applicable in other operating environments in which aserver system provides data processing for monitoring and facilitatingreview of data captured by other types of electronic devices (e.g.,smart thermostats 102, smart hazard detectors 104, smart doorbells 106,smart wall plugs 110, appliances 112 and the like).

The electronic devices, the client devices or the server systemcommunicate with each other using the one or more communication networks162. In an example smart home environment, two or more devices (e.g.,the network interface device 160, the hub device 180, and the clientdevices 504-m) are located in close proximity to each other, such thatthey could be communicatively coupled in the same sub-network 162A viawired connections, a WLAN or a Bluetooth Personal Area Network (PAN).The Bluetooth PAN is optionally established based on classical Bluetoothtechnology or Bluetooth Low Energy (BLE) technology. This smart homeenvironment further includes one or more other radio communicationnetworks 162B through which at least some of the electronic devices ofthe video sources 522-n exchange data with the hub device 180.Alternatively, in some situations, some of the electronic devices of thevideo sources 522-n communicate with the network interface device 160directly via the same sub-network 162A that couples devices 160, 180 and504-m. In some implementations (e.g., in the network 162C), both theclient device 504-m and the electronic devices of the video sources522-n communicate directly via the network(s) 162 without passing thenetwork interface device 160 or the hub device 180.

In some implementations, during normal operation, the network interfacedevice 160 and the hub device 180 communicate with each other to form anetwork gateway through which data are exchanged with the electronicdevice of the video sources 522-n. As explained above, the networkinterface device 160 and the hub device 180 optionally communicate witheach other via a sub-network 162A.

FIG. 6 is a block diagram illustrating a representative hub device 180in accordance with some implementations. In some implementations, thehub device 180 includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 602, one or more communicationinterfaces 604, memory 606, radios 640, and one or more communicationbuses 608 for interconnecting these components (sometimes called achipset). In some implementations, the hub device 180 includes one ormore input devices 610 such as one or more buttons for receiving input.In some implementations, the hub device 180 includes one or more outputdevices 612 such as one or more indicator lights, a sound card, aspeaker, a small display for displaying textual information and errorcodes, etc. Furthermore, in some implementations, the hub device 180uses a microphone and voice recognition or a camera and gesturerecognition to supplement or replace the keyboard. In someimplementations, the hub device 180 includes a location detection device614, such as a GPS (global positioning satellite) or other geo-locationreceiver, for determining the location of the hub device 180.

The hub device 180 optionally includes one or more built-in sensors (notshown), including, for example, one or more thermal radiation sensors,ambient temperature sensors, humidity sensors, IR sensors, occupancysensors (e.g., using RFID sensors), ambient light sensors, motiondetectors, accelerometers, and/or gyroscopes.

The radios 640 enable and/or connect to one or more radio communicationnetworks in the smart home environments, and allow a hub device tocommunicate with smart devices 204. In some implementations, the radios640 are capable of data communications using any of a variety of customor standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee,6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART,MiWi, etc.) custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), and/or any other suitable communication protocol,including communication protocols not yet developed as of the filingdate of this document. In some implementations, the radios 640 includemultiple different physical radios, each of which implements a differentcommunication protocol. For example, in some implementations the radios640 include a Wi-Fi radio, a Bluetooth radio and an IEEE 802.15.4 radio,all of which operate at 2.4 GHz. In some implementations, some of theradios are combined. For example, in some implementations, a Bluetoothradio and a Wi-Fi radio are incorporated in a single chip coupled to asingle antenna. In other implementations, a Bluetooth radio and an IEEE802.15.4 radio are incorporated in a single chip coupled to a singleantenna. Any combination of these radios can be implemented in any ofthe smart devices employed in a smart home environment.

Communication interfaces 604 include, for example, hardware capable ofinterfacing the one or more radios 640 with the hub device 180, so as toenable data communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 606 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 606, or alternatively the non-volatile memorywithin memory 606, includes a non-transitory computer readable storagemedium. In some implementations, memory 606, or the non-transitorycomputer readable storage medium of memory 606, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 616 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Hub device communication module 618 for connecting to and        communicating with other network devices (e.g., network        interface 160, such as a router that provides Internet        connectivity, networked storage devices, network routing        devices, server system 508, etc.) connected to one or more        networks 162 via one or more communication interfaces 604 (wired        or wireless);    -   Radio Communication Module 620 for connecting the hub device 180        to other devices (e.g., controller devices, smart devices 204 in        smart home environment 100, client devices 504) via one or more        radio communication devices (e.g., radios 640);    -   User interface module 622 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed; and    -   Hub device database 624, including but not limited to:        -   Sensor information 6240 for storing and managing data            received, detected, and/or transmitted by one or more            sensors of the hub device 180 and/or one or more other            devices (e.g., smart devices 204 in smart home environment            100);        -   Device settings 6242 for storing operational settings for            one or more devices (e.g., coupled smart devices 204 in            smart home environment 100); and        -   Communication protocol information 6244 for storing and            managing protocol information for one or more protocols            (e.g., standard wireless protocols, such as ZigBee, Z-Wave,            etc., and/or custom or standard wired protocols, such as            Ethernet).

Each of the above identified elements (e.g., modules stored in memory206 of hub device 180) may be stored in one or more of the previouslymentioned memory devices (e.g., the memory of any of the smart devicesin smart home environment 100, FIG. 1), and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory606, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 606, optionally, stores additionalmodules and data structures not described above.

FIG. 7 is a block diagram illustrating the hub server system 508 inaccordance with some implementations. The hub server system 508,typically, includes one or more processing units (CPUs) 702, one or morenetwork interfaces 704 (e.g., including an I/O interface to one or moreclient devices and an I/O interface to one or more electronic devices),memory 706, and one or more communication buses 708 for interconnectingthese components (sometimes called a chipset). Memory 706 includeshigh-speed random access memory, such as DRAM, SRAM, DDR RAM, or otherrandom access solid state memory devices; and, optionally, includesnon-volatile memory, such as one or more magnetic disk storage devices,one or more optical disk storage devices, one or more flash memorydevices, or one or more other non-volatile solid state storage devices.Memory 706, optionally, includes one or more storage devices remotelylocated from one or more processing units 702. Memory 706, oralternatively the non-volatile memory within memory 706, includes anon-transitory computer readable storage medium. In someimplementations, memory 706, or the non-transitory computer readablestorage medium of memory 706, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 710 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 712 for connecting the hub server        system 508 to other systems and devices (e.g., client devices,        electronic devices, and systems connected to one or more        networks 162, FIGS. 1-5) via one or more network interfaces 704        (wired or wireless);    -   Server-side module 714, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 7140 for receiving data from            electronic devices (e.g., video data from a camera 118,            FIG. 1) via the hub device 180, and preparing the received            data for further processing and storage in the data storage            database 7160;        -   Hub and device control module 7142 for generating and            sending server-initiated control commands to modify            operation modes of electronic devices (e.g., devices of a            smart home environment 100), and/or receiving (e.g., from            client devices 504) and forwarding user-initiated control            commands to modify operation modes of the electronic            devices;        -   Data processing module 7144 for processing the data provided            by the electronic devices, and/or preparing and sending            processed data to a device for review (e.g., client devices            504 for review by a user); and    -   Server database 716, including but not limited to:        -   Data storage database 7160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            hub device 180 or smart devices are stored securely;        -   Account database 7162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles; and        -   Device Information Database 7164 for storing device            information related to one or more hub devices, e.g., device            identifiers and hub device specific secrets, independently            of whether the corresponding hub devices have been            associated with any user account.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory706, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 706, optionally, stores additionalmodules and data structures not described above.

FIG. 8 is a block diagram illustrating a representative client device504 associated with a user account in accordance with someimplementations. The client device 504, typically, includes one or moreprocessing units (CPUs) 802, one or more network interfaces 804, memory806, and one or more communication buses 808 for interconnecting thesecomponents (sometimes called a chipset). Optionally, the client devicealso includes a user interface 810 and one or more built-in sensors 890(e.g., accelerometer and gyroscope). User interface 810 includes one ormore output devices 812 that enable presentation of media content,including one or more speakers and/or one or more visual displays. Userinterface 810 also includes one or more input devices 814, includinguser interface components that facilitate user input such as a keyboard,a mouse, a voice-command input unit or microphone, a touch screendisplay, a touch-sensitive input pad, a gesture capturing camera, orother input buttons or controls. Furthermore, some the client devicesuse a microphone and voice recognition or a camera and gesturerecognition to supplement or replace the keyboard. In someimplementations, the client device includes one or more cameras,scanners, or photo sensor units for capturing images (not shown).Optionally, the client device includes a location detection device 816,such as a GPS (global positioning satellite) or other geo-locationreceiver, for determining the location of the client device.

Memory 806 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 806, optionally, includes one or more storagedevices remotely located from one or more processing units 802. Memory806, or alternatively the non-volatile memory within memory 806,includes a non-transitory computer readable storage medium. In someimplementations, memory 806, or the non-transitory computer readablestorage medium of memory 806, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 818 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 820 for connecting the client        device 504 to other systems and devices (e.g., client devices,        electronic devices, and systems connected to one or more        networks 162, FIGS. 1-5) via one or more network interfaces 804        (wired or wireless);    -   Input processing module 822 for detecting one or more user        inputs or interactions from one of the one or more input devices        814 and interpreting the detected input or interaction;    -   One or more applications 824 for execution by the client device        (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications)        for controlling devices (e.g., sending commands, configuring        settings, etc. to hub devices and/or other client or electronic        devices) and for reviewing data captured by the devices (e.g.,        device status and settings, captured data, or other information        regarding the hub device or other connected devices);    -   User interface module 622 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed;    -   Client-side module 828, which provides client-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Hub device and device control module 8280 for generating            control commands for modifying an operating mode of the hub            device or the electronic devices in accordance with user            inputs; and        -   Data review module 8282 for providing user interfaces for            reviewing data processed by the hub server system 508; and    -   Client data 830 storing data associated with the user account        and electronic devices, including, but is not limited to:        -   Account data 8300 storing information related to both user            accounts loaded on the client device and electronic devices            (e.g., of the video sources 522) associated with the user            accounts, wherein such information includes cached login            credentials, hub device identifiers (e.g., MAC addresses and            UUIDs), electronic device identifiers (e.g., MAC addresses            and UUIDs), user interface settings, display preferences,            authentication tokens and tags, password keys, etc.; and        -   Local data storage database 8302 for selectively storing raw            or processed data associated with electronic devices (e.g.,            of the video sources 522, such as a camera 118).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, modules or datastructures, and thus various subsets of these modules may be combined orotherwise re-arranged in various implementations. In someimplementations, memory 806, optionally, stores a subset of the modulesand data structures identified above. Furthermore, memory 806,optionally, stores additional modules and data structures not describedabove.

FIG. 9 is a block diagram illustrating a representative smart device 204in accordance with some implementations. In some implementations, thesmart device 204 (e.g., any device of a smart home environment 100(FIGS. 1 and 2), such as a camera 118, a smart hazard detector 104, asmart thermostat 102, hub device 180, etc.) includes one or moreprocessing units (e.g., CPUs, ASICs, FPGAs, microprocessors, and thelike) 902, memory 906, a communications module 942 that includes one ormore radios 940 and radios 950, communication interfaces 904, and one ormore communication buses 908 for interconnecting these components(sometimes called a chipset). In some implementations, user interface910 includes one or more output devices 912 that enable presentation ofmedia content, including one or more speakers and/or one or more visualdisplays. In some implementations, user interface 910 also includes oneor more input devices 914, including user interface components thatfacilitate user input such as a keyboard, a mouse, a voice-command inputunit or microphone, a touch screen display, a touch-sensitive input pad,a gesture capturing camera, or other input buttons or controls.Furthermore, some smart devices 204 use a microphone and voicerecognition or a camera and gesture recognition to supplement or replacethe keyboard. In some implementations, the smart device 204 includes oneor more image/video capture devices 918 (e.g., cameras, video cameras,scanners, photo sensor units). Optionally, the client device includes alocation detection device 916, such as a GPS (global positioningsatellite) or other geo-location receiver, for determining the locationof the smart device 204.

The built-in sensors 990 include, for example, one or more thermalradiation sensors, ambient temperature sensors, humidity sensors, IRsensors, occupancy sensors (e.g., using RFID sensors), ambient lightsensors, motion detectors, accelerometers, and/or gyroscopes.

The radio(s) 940 and radio(s) 950 enable one or more radio communicationnetworks in the smart home environments, and allow a smart device 204 tocommunicate with other devices. In some implementations, the radios 940are capable of data communications using any of a variety of custom orstandard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee,6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART,MiWi, etc.) custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), and/or any other suitable communication protocol,including communication protocols not yet developed as of the filingdate of this document.

Communication interfaces 950 include, for example, hardware capable ofinterfacing the one or more radios 940 and 950 with the smart device204, so as to enable data communications using any of a variety ofcustom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi,ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a,WirelessHART, MiWi, etc.) and/or any of a variety of custom or standardwired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document. In someimplementations, each radio(s) 940 and radio(s) 950 has a respectivecommunication interface 950 for facilitating and managing datacommunications for the respective radio, while in other implementations,multiple radios 940 and/or 950 are managed by a single respectivecommunication interface 950.

In some implementations, radios 940 and/or radios 950 are configured totransmit and receive the same or distinct types of signals in the smarthome environment. For example, radios 940 may include transceiversconfigured to transmit data between other devices (e.g., smart devices)within the smart home environment (e.g., IEEE 802.15.4 communicationsprotocol for unilaterally/bilaterally transmitting data between andamong smart devices). Signals transmitted between devices may include,for example, signals directed to critical hazard information (e.g.,pings indicating the detection of smoke) or device status information(e.g., ping indicating low battery). In contrast, in someimplementations, the radios 950 may include transceivers configured totransmit high-bandwidth data across data networks (e.g., IEEE 802.11(Wi-Fi) for uploading a video stream to a smart home provider serversystem 164). In some implementations, the radios 940 and/or the radios950 include transceivers configured for close-range communications withdevices (e.g., Bluetooth communications protocol for deviceprovisioning). In some implementations, the radios 940 and/or the radios950 include transceivers configured to transmit low-power signals (e.g.,smart hazard detectors 104 not connected to a persistent power source).In some implementations, radios 940 and/or radios 950 are configured totransmit multiple types of signals in the smart home environment (e.g.,a Wi-Fi radio 950 uploads video stream data to the smart home providerserver system 164, in addition to routing received beacons to othernearby smart devices). In some implementations, the radios 940 and/orthe radios 950 of a respective device include transceivers for directlyand communicably bridging the respective device to other devices (e.g.,pairing devices directly via Bluetooth, rather than communicating via arouter by using Wi-Fi). In some implementations, the radios 940 and/orthe radios 950 are configured to translate signals received through afirst radio 940, and further to re-transmit the translated signals usingthe first radio 940 and/or a radio 950 (e.g., a proprietary messageformat is received via Bluetooth and translated, where the translatedmessages are re-transmitted to other devices using Wi-Fi).

The communications module 942 includes a variety of components forenabling the receiving and transmitting of signals by a respective smartdevice 204, including one or more amplifiers, oscillators, antennas,filters, switches, memory, firmware, and/or any other support circuitsor circuit components. In some implementations, the one or more radios940 and radios 950 are integrated components of the communicationsmodule 942 (e.g., System on a Chip (SOC)). In some implementations, theone or more radios 940 and radios 950 have respective circuit components(e.g., radios 940 having a corresponding antenna 1402-1, radios 950having a corresponding antenna 1402-2). Alternatively, the one or moreradios 940 and radios 950 share one or more circuit components (e.g.,radio 950-1 and radio 950-2 sharing an antenna 1402-2, FIG. 15B).

Memory 906 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 906, or alternatively the non-volatile memorywithin memory 906, includes a non-transitory computer readable storagemedium. In some implementations, memory 906, or the non-transitorycomputer readable storage medium of memory 906, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 920 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Device communication module 922 for connecting to and        communicating with other network devices (e.g., network        interface 160, such as a router that provides Internet        connectivity, networked storage devices, network routing        devices, server system 508, etc.) connected to one or more        networks 162 via one or more communication interfaces 904 (wired        or wireless);    -   Radio Communication Module 924 for connecting the smart device        204 to other devices (e.g., controller devices, smart devices        204 in smart home environment 100, client devices 504) via one        or more radio communication devices (e.g., radios 940)    -   Input processing module 926 for detecting one or more user        inputs or interactions from the one or more input devices 914        and interpreting the detected inputs or interactions;    -   User interface module 928 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., the smart device 204, and/or        other devices in smart home environment 100) can be configured        and/or viewed;    -   One or more applications 930 for execution by the smart device        930 (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications)        for controlling devices (e.g., executing commands, sending        commands, and/or configuring settings of the smart device 204        and/or other client/electronic devices), and for reviewing data        captured by devices (e.g., device status and settings, captured        data, or other information regarding the smart device 204 and/or        other client/electronic devices);    -   Device-side module 932, which provides device-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Command receiving module 9320 for receiving, forwarding,            and/or executing instructions and control commands (e.g.,            from a client device 504, from a smart home provider server            system 164, from user inputs detected on the user interface            910, etc.) for operating the smart device 204; and        -   Data processing module 9322 for processing data captured or            received by one or more inputs (e.g., input devices 914,            image/video capture devices 918, location detection device            916), sensors (e.g., built-in sensors 990), interfaces            (e.g., communication interfaces 904, radios 940), and/or            other components of the smart device 204, and for preparing            and sending processed data to a device for review (e.g.,            client devices 504 for review by a user);    -   Device data 934 storing data associated with devices (e.g., the        smart device 204), including, but is not limited to:        -   Account data 9340 storing information related to user            accounts loaded on the smart device 204, wherein such            information includes cached login credentials, smart device            identifiers (e.g., MAC addresses and UUIDs), user interface            settings, display preferences, authentication tokens and            tags, password keys, etc.; and        -   Local data storage database 9342 for selectively storing raw            or processed data associated with the smart device 204            (e.g., video surveillance footage captured by a camera 118);    -   Bypass module 936 for detecting whether radio(s) 940 and/or        radio(s) 950 are transmitting signals via respective antennas        coupled to the radio(s) 940 and/or radio(s) 950 (e.g., detecting        whether radio 950 is transmitting via antenna 1402-2) and to        accordingly couple radio(s) 940 and/or radio(s) 950 to their        respective antennas either via a bypass line (e.g., bypass line        1408) or an amplifier (e.g., low noise amplifier 1406-2); and    -   Transmission access module 938 for granting or denying        transmission access to one or more radio(s) 940 and/or radio(s)        950 (e.g., based on detected control signals and transmission        requests).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. For example, insome implementations, the one or more radios 940 and radios 950 includerespective memory and firmware for storing one or moreprograms/executable modules of the memory 906. The above identifiedmodules or programs (i.e., sets of instructions) need not be implementedas separate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise re-arranged invarious implementations. In some implementations, memory 906,optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 906, optionally, stores additionalmodules and data structures not described above.

FIG. 10 is a block diagram illustrating the smart home provider serversystem 164 in accordance with some implementations. The smart homeprovider server system 164, typically, includes one or more processingunits (CPUs) 1002, one or more network interfaces 1004 (e.g., includingan I/O interface to one or more client devices and an I/O interface toone or more electronic devices), memory 1006, and one or morecommunication buses 1008 for interconnecting these components (sometimescalled a chipset). Memory 1006 includes high-speed random access memory,such as DRAM, SRAM, DDR RAM, or other random access solid state memorydevices; and, optionally, includes non-volatile memory, such as one ormore magnetic disk storage devices, one or more optical disk storagedevices, one or more flash memory devices, or one or more othernon-volatile solid state storage devices. Memory 1006, optionally,includes one or more storage devices remotely located from one or moreprocessing units 1002. Memory 1006, or alternatively the non-volatilememory within memory 1006, includes a non-transitory computer readablestorage medium. In some implementations, memory 1006, or thenon-transitory computer readable storage medium of memory 1006, storesthe following programs, modules, and data structures, or a subset orsuperset thereof:

-   -   Operating system 1010 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 1012 for connecting the smart home        provider server system 164 to other systems and devices (e.g.,        client devices, electronic devices, and systems connected to one        or more networks 162, FIGS. 1-5) via one or more network        interfaces 1004 (wired or wireless);    -   Server-side module 1014, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 10140 for receiving data from            electronic devices (e.g., video data from a camera 118, FIG.            1), and preparing the received data for further processing            and storage in the data storage database 10160;        -   Device control module 10142 for generating and sending            server-initiated control commands to modify operation modes            of electronic devices (e.g., devices of a smart home            environment 100), and/or receiving (e.g., from client            devices 504) and forwarding user-initiated control commands            to modify operation modes of the electronic devices;        -   Data processing module 10144 for processing the data            provided by the electronic devices, and/or preparing and            sending processed data to a device for review (e.g., client            devices 504 for review by a user); and    -   Server database 1016, including but not limited to:        -   Data storage database 10160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            electronic devices are stored securely; and        -   Account database 10162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory1006, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 1006, optionally, storesadditional modules and data structures not described above.

Furthermore, in some implementations, the functions of any of thedevices and systems described herein (e.g., hub device 180, hub serversystem 508, client device 504, smart device 204, smart home providerserver system 164) are interchangeable with one another and may beperformed by any other devices or systems, where the correspondingsub-modules of these functions may additionally and/or alternatively belocated within and executed by any of the devices and systems. Thedevices and systems shown in and described with respect to FIGS. 6-10are merely illustrative, and different configurations of the modules forimplementing the functions described herein are possible in variousimplementations.

As described with respect to FIGS. 6-10, devices in a smart homeenvironment (e.g., smart devices 204 in FIG. 2, such as cameras 118,smart thermostats 102, smart hazard detectors 104, etc. of a smart homeenvironment 100, FIG. 1) include a host of circuit components andinterfaces for enabling communications with other systems, devices,and/or servers. For example, in some implementations, smart devicesinclude a communications module (e.g., communications module 942, FIG.9) which comprises one or more radios 940 and/or radios 950 forreceiving and transmitting signals to other devices and across networks(sometimes referred to generally as “transceivers” or “transceiverdevices”). In some implementations, the one or more radios 940 andradios 950 are components of a single integrated circuit (e.g., Systemon a Chip (SOC)). Given the typical physical compactness of smartdevices, components of the communications module 942 and othercomponents of the device are often collocated in close physicalproximity with one another. For example, a typical smart device maycontain multiple radio antennas, memory devices, sensors, chips, andother electronic components. As a consequence of their close physicalspacing within smart devices, however, and in combination withcomponents coming into close contact with conductive materials (e.g.,metal casing, camera stand, wires, etc.), device components, such asantennas, are typically poorly isolated from transmissions of oneanother. Additionally, because these devices sometimes share the same orclose frequency bands in operation (e.g., IEEE 802.11 (i.e., Wi-Fi) and802.15.4 sharing 2.4 GHz frequency band), signals transmitted by onecomponent tend to interfere with signals transmitted and/or received byother components. Ultimately, components of the communications module942 typically achieve poor signal-to-noise ratio (SNR), distortion,degraded analog signal quality, and increased bit error rate (BER).

Furthermore, the poor isolation of these devices has an additionalimpact on the maximum input power of device components, since thetransmission power of signals transmitting by one transceiver addsunexpectedly to the expected transmission of signals simultaneouslyreceived by other nearby transceivers. Sensitive device components arethus often risk of damage when their input power thresholds areexceeded. For example, referring to the front end module 1400 of thesmart device 204 in FIG. 14, the low noise amplifier 1406-2 typicallyoffers higher sensitivity to received signals, but consequently has alower input power threshold than alternative amplifiers. Thus, thetransmission power of antenna 1402-2, which adds to the transmissionpower of any signals received by antenna 1402-1, risks damagingcomponents such as the low noise amplifier 1406-2.

Various schemes and techniques are described for lessening the harmfuleffects arising from poorly isolated transceivers in smart devices, astrategy generally referred to as coexistence. In particular, FIGS.11-13 illustrate various component layout strategies for achievingimproved coexistence for various devices, in accordance with someimplementations. Furthermore, FIG. 14 illustrates a block diagram of acommunications module 942 of a smart device utilizing bypass circuitry,and FIG. 22 is a flow diagram illustrating a method of coexistence usingbypass circuitry, in accordance with some implementations. Moreover,FIGS. 15A-15L illustrate the use of control signals in a coexistencescheme, and FIGS. 23A-23F are flow diagrams illustrating methods ofusing control signals in a coexistence scheme, in accordance with someimplementations.

Implementations and techniques described with respect to FIGS. 11through 15 may be combined in whole or in part to achieve improvedcoexistence. For example, implementations described with respect toFIGS. 15A-15L (and corresponding methods of operation) may serve as anadditional or supplementary measures for achieving optimal coexistenceand operation of multiple radios in the event that implementationsdescribed with respect to FIG. 14 fail or malfunction (e.g., if thecommunications module 942 fails to engage the bypass line 1408,coexistence can still be achieved through software/firmware-basedimplementations described in 15A-15L).

FIGS. 11A-11M illustrate various assembly views of a camera device 118,in accordance with some implementations. In particular, the embodimentsillustrate the placement of the components as part of a component layoutstrategy for achieving improved coexistence. Components of a camera 118(e.g., where the camera is a smart device 204, FIG. 9) and variousimplementations are described in greater detail throughout (e.g., FIGS.9, 14, and 15).

Specifically, FIGS. 11A and 11B illustrate perspective views of anassembled camera device 118. The camera device 118 captures multimediadata (image, video, and audio data) in real-time, and communicates rawor processed multimedia data to its users via a remote surveillanceserver. The captured raw multimedia data are optionally processedlocally in the camera device 118 or remotely within the remotesurveillance server.

FIG. 11C illustrates a view of the camera device 118 in which theplastic cover 1102 is removed from the camera device 118 assembly. FIGS.11D and 11E further illustrate views of the camera device 118 and thelocations in which one or more antennas (e.g., 1104-1 and 1104-2) arepositioned with respect to the plastic cover 1102 of the camera device118 assembly. As shown in FIG. 11D, a cable (e.g., RF coaxial cable)connects the antenna 1104-2 to the main circuit board of the cameradevice 118 (which is illustrated with greater detail in FIGS. 11H and11I. Although not shown, in some implementations, the antenna 1104-1 isalso connected to the main circuit board using a similar cable.

The placement of antennas 1104 within the camera device 118 assembly issuch that interference from conductive and transmitting components isminimized. Placement of antennas 1104 is based at least in part on thetype of antennas used. In some implementations, antennas may beintegrated into or secured by stickers or tape (or alternatively fixedusing a non-conductive adhesive). By selecting the material of theenclosed housing of the camera assembly to be a less (or non) conductivematerial, such as plastic (e.g., plastic cover 1102), these antennas maybe fixed adhesively along the inside of the enclosing housing, therebyreducing the impact of interference otherwise experienced. Antennas 1104may also be stamped sheet metal antennas. These antennas may beconstructed as three-dimensional sheet metal antennas that are mountedon the circuit board where nearby the location of the correspondingtransceiver. An example is a Planar Inverted-F Antenna (PIFA) stampedmetal antenna. Alternatively, antennas 1104 may be trace antennasintegrated into/onto a printed circuit board (PCB). In someimplementations, the trace is laminated on the surface of the PCD. Inother cases, the traces may occupy several layers of a multilayer board.Chip antennas may also be used, which are passive surface mountedantenna components often made from ceramic. Optionally, antennas 1104may be antennas external to the enclosed housing of the camera assembly.

FIG. 11F is an exploded view of a camera device 118 in accordance withsome implementations. This view of the camera device 118 illustrates acamera lens 1108, a plurality of LEDs 1106, the one or more antennas1104.

In accordance with a regular monitor mode, the camera device 118 isconfigured to provide video monitoring and security in a smart homeenvironment that is illuminated by visible light sources (e.g., the sunor light bulbs). In some implementations, the camera device 118 includesalternative operation modes, such as a night vision mode and a depthimaging mode. Each of the alternative operation modes is associated witha respective illumination condition. For example, in the night visionmode, the camera device 118 is configured to capture activities in thesmart home environment at night when no or limited visible lightillumination is available. In the depth imaging mode, the camera device118 is configured to create a depth map or image for the correspondingfield of view in the smart home environment. The depth map can besubsequently used in the regular monitor mode for accurateidentification of objects in the smart home environment. In someimplementations, the depth image is created based on one or more imagescaptured when part of the field of view is selectively illuminated.Therefore, in some implementations, the camera device 118 is configuredto include a LED illumination system, and use it as an internal lightsource to provide illumination in the smart home environment accordingto the respective illumination condition associated with eachalternative operation mode of the camera device 118.

Specifically, in some implementations, the plurality of LEDs 1106includes infrared LEDs 1106. The infrared LEDs 1106 are enclosed withina dark-colored, infrared-transparent plastic cover 1102 of the cameradevice 118, and therefore are invisible from the exterior of the cameradevice 118. Given that the plastic cover 1102 permits infrared light topass through it, the camera device 118 can rely on the infrared LEDs1106 to provide illumination at night. In the night vision mode, theplurality of LEDs is powered on to illuminate the field of view withinfrared light at night. The camera device 118 includes infrared imagesensors that capture infrared images or video clips of the field ofview. In the depth imaging mode, the plurality of LEDs 1106 is groupedinto a number of LED sets, and each LED set is selectively powered up toilluminate respective part of a field of view associated with a venuewhere the camera device 118 is located. Images captured in associationwith these LED sets are combined to generate a depth map of the entirefield of view at the venue.

Alternatively, in some implementations, the plurality of LEDs 1106 is amix of infrared and visible light LEDs, including at least one infraredLED and at least one visible light LED. In the night vision mode, the atleast one infrared LED of the plurality of LEDs is powered on toilluminate the field of view with infrared light.

In some implementations, the plurality of LEDs 1106 is disposed on aninternal assembly structure of the camera device 118, and configured tosurround the camera lens 1108 of the camera device 118. In someimplementations, as shown in the inset of FIG. 11F, each LED isoptionally tilted with an angle with respect to the optical axis thatpasses through a center 340 of the camera lens 1108. Here, the opticalaxis is perpendicular to the lens surface at the center of the cameralens 1108. In some implementations, each LED is tilted away from theoptical axis of the camera with the angle in the range of 20-40 degrees.In this example, the plurality of LEDs 1106 includes eight LEDs that aregrouped in four pairs of LEDs. The four pairs of LEDs are disposedsymmetrically within four quadrants surrounding the camera lens 1108. Insome implementations, a mechanical or electrical component 314 is placedbetween two LED pairs or between two LEDs within a LED pair. It is notedthat the camera lens 1108 can be surrounded by a number of LEDs having adifferent physical arrangement from the above example (e.g., the cameralens 1108 is surround by a hundred LEDs distributed uniformly in threelayers surrounding the camera lens 1108).

In some implementations, the one or more antennas 1104 are attached onan interior wall of the camera cover 1102 according to the form factorof the camera device 118. Each of the one or more antennas 1104 ispositioned at a respective preferred location with a respectivepreferred orientation with respect to the other antennas to suppress orreduce the impact from the presence and interference of the otherantennas. In some situations, the receiving element 206 and the baseassembly 208 are made from metal material, and each of the one or moreantennas 1104 is positioned at a respective preferred location with arespective preferred orientation with respect to the receiving element206 and the base assembly 208 to suppress or reduce the impact fromtheir presence. To render the preferred location and orientation, eachof the one or more antennas 1104 is marked with a respective alignmentmark that is configured to guide assembly of the respective antenna ontothe interior wall of the camera cover 1102.

In some implementations, the one or more antennas include at least afirst antenna and a second antenna. The first antenna is configured towirelessly transfer data captured by the camera device 118 over awireless local area network (WLAN), and the second antenna is configuredto communicate configuration data associated with the WLAN via a firstradio network for the purposes of commissioning the camera device 118into the WLAN. In some implementations, the camera device 118 furtherincludes a third antenna to allow the camera device 118 to communicatewith a local hub device (e.g., the hub device 180 shown in FIG. 1) via asecond radio network that is distinct from the first radio network. Insome implementations, the WLAN and the first and second radio networksare associated with custom or standard wireless protocols (e.g., IEEE802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart,ISA100.11a, WirelessHART, MiWi, etc.). In a specific example, the first,second and third antennas are configured to transfer their respectivedata wirelessly according to IEEE 802.11, IEEE 802.15.4 and ZigBeespecifications, respectively.

Further, in some implementations, the one or more antennas 1104 areelectrically coupled to separate wireless transmitter circuits thatoperate on distinct frequency bands, and transmit wireless signals atthe distinct frequency bands concurrently. In some implementations, theone or more antennas 1104 are electrically coupled to a duplex filter,or a switch that controls their connections to a single wirelessreceiver circuit.

FIGS. 11G-11M illustrate additional views of the camera device 118.Particularly, FIG. 11G illustrates exploded views of the camera device118. FIGS. 11H and 11I illustrate top and bottom views, respectively, ofa main circuit board of the camera device 118. Additionally, FIGS. 11Jand 11K illustrate top and bottom views, respectively, of a sensor boardof the camera device 118. Moreover, FIGS. 11L and 11M illustrate top andbottom views, respectively, of an IR LED circuit board of the cameradevice 118.

In some implementations, a camera assembly includes an enclosed housinghaving a rear surface, a front surface, and a periphery (e.g., camera118, FIGS. 11A-11M). In some implementations, the camera assemblyfurther includes a lens module located within the housing and configuredto receive light via the front surface (e.g., lens 1108, FIG. 11F). Insome implementations, video data captured by the lens module isexchanged between the camera assembly and a server using a wirelesslocal area network.

In some implementations, the camera assembly further includescommunication circuitry located within the housing and configured towireless communicate over a plurality of different communicationprotocols (e.g., main circuit board of the camera device 118 thatincludes multiple transceivers). In some implementations, thecommunication circuitry includes a first circuit configured forcommunication over the first communication protocol (e.g., Wi-Fitransceiver) and a second circuit configured for communication over thesecond communication protocol (e.g., 802.15.4 transceiver), wherein thefirst circuit and the second circuit are distinct. In someimplementations, the communication circuitry is an integrated circuitconfigured for communication over both the first and secondcommunication protocols (e.g., radios 950, which includes a radio 950-1for Bluetooth LE, and a radio 950-2 for Wi-Fi, FIG. 15B). In someimplementations, the communication circuitry is configured to wirelesscommunicate over at least three different communication protocols (e.g.,Wi-Fi, 802.15.4, and Bluetooth LE). In some implementations, the secondantenna is further configured for communication over a third one of thecommunication protocols. In some implementations, the communicationcircuitry is further configured to provide transmission access forcommunicating over the first communication protocol while denyingtransmission access for communicating over the second communicationprotocol, while detecting an activated priority control signal (e.g.,using control signals as described with respect to FIGS. 15A-15L).

In some implementations, the camera assembly further includes a firstantenna arranged at a first location on an inner surface of theperiphery (e.g., antenna 1104-1), the first antenna configured forcommunication over a first one of the communication protocols (e.g.,Wi-Fi), and a second antenna (e.g., antenna 1104-2) arranged at a secondlocation on the inner surface of the periphery, the second locationbeing different than the first location, the second antenna configuredfor communication over a second one of the communication protocols(e.g., 802.15.4). In some implementations, the first antenna is arrangedat the first location on the inner surface of the periphery and/or thesecond antenna is arranged at the second location on the inner surfaceof the periphery by an adhesive material (e.g., FIG. 11E). In someimplementations, the first antenna has a first orientation and thesecond antenna has a second orientation such that the impact from thepresence and interference of each other antenna are suppressed (e.g.,orienting antennas 1104-1 and 1104-2 and different angles with respectto each other and other components within the camera assembly). In someimplementations, the first antenna and the second antenna are markedwith a respective alignment mark that is configured to guide theassembly of the respective antenna onto the interior wall of the cameralid.

In some implementations, the first antenna and the second antenna areconfigured to operate at the same frequency (e.g., 2.4 GHz). In someimplementations, the first antenna and the second antenna are configuredto operate at distinct frequencies (e.g., 2.4 GHz and 5 GHz). In someimplementations, the first antenna is configured to transmit andreceive, over the first communication protocol, signals comprising oneor more of alerts, control signals and status information to and fromother smart home devices (e.g., emergency alerts from a hazard detector104 using 802.15.4, or any signals transmitted/received by any of thesmart devices 204 described with respect to FIGS. 1-13). Furthermore,the second antenna is configured to transmit and receive, over thesecond communication protocol signals for configuring the smart homedevice (e.g., Bluetooth LE for provisioning and setting up the camera118), and over the third communication protocol data corresponding tovideo captured by the smart home device (e.g., Wi-Fi for streaming videodata).

In some implementations, the first antenna or the second antenna isconfigured to transmit and receive wireless signals in a wireless localarea network according to the IEEE 802.11 specifications. In someimplementations, wherein the first antenna or the second antenna isconfigured to transmit and receive wireless signals in a wirelesspersonal area network according to the IEEE 802.15.4 standard. In someimplementations, the first antenna or the second antenna is configuredto transmit and receive wireless signals according to the Bluetooth LowEnergy standard. In some implementations, the first antenna and thesecond antenna are electrically coupled to a duplex that controls theirconnections to a single wireless receiver circuit.

In some implementations, the camera assembly further includes a loop armthat is configured to hold the enclosed housing when the enclosedhousing is inserted within a cutout opening in the loop arm. In someimplementations, the loop arm is made from metal material, and the firstlocation of the first antenna and the second location of the secondantenna are such that the impact from the presence of the metal loop armis suppressed (e.g., placed in a location that is farthest from thelocation at which the loop arm and the enclosed housing make contact).

FIGS. 12A-12C illustrate various views of a smart thermostat (e.g.,smart thermostat 102, FIG. 1) that may be used as part of a smart homeenvironment 100, as previously described.

Specifically, FIG. 12A illustrates an exploded perspective view of thesmart thermostat 102 with respect to its two main components, which arethe head unit 1200-A and the back plate 1200-B. The head unit 1200-Aincludes a head unit circuit board 1250 (described in further detailwith respect to FIG. 12B), and the back plate 1200-B includes abackplate circuit board 1260 (described in further detail with respectto FIG. 12C). Further technical and/or functional descriptions ofvarious ones of the electrical and mechanical components illustratedhereinbelow can be found in one or more of the commonly assignedincorporated applications, such as U.S. Ser. No. 13/199,108, supra. Inthe drawings shown, the “z” direction is outward from the wall, the “y”direction is the head-to-toe direction relative to a walk-up user, andthe “x” direction is the user's left-to-right direction.

FIG. 12B illustrates a head-on view of the head unit circuit board 1250for the smart thermostat, which comprises a head unit microprocessor1202 (such as a Texas Instruments AM3703 chip) and an associatedoscillator 1204, along with DDR SDRAM memory 1206, and mass NAND storage1208. For Wi-Fi capability, there is provided in a separate compartmentof RF shielding 1210 a Wi-Fi module 1212, such as a Murata WirelessSolutions LBWA19XSLZ module, which is based on the Texas InstrumentsWL1270 chipset supporting the 802.11 b/g/n WLAN standard. For the Wi-Fimodule 1212 is supporting circuitry 1214 including an oscillator 1216.For ZigBee capability, there is provided also in a separately shieldedRF compartment a ZigBee module 1218, which can be, for example, aC2530F256 module from Texas Instruments. For the ZigBee module 1218there is provided supporting circuitry 1220 including an oscillator 1222and a low-noise amplifier 1224. Also provided is display backlightvoltage conversion circuitry 1226, piezoelectric driving circuitry 1228,and power management circuitry 1230 (local power rails, etc.). Providedon a flex circuit 1232 that attaches to the back of the head unitcircuit board by a flex circuit connector 1234 is a proximity andambient light sensor (PROX/ALS), more particularly a Silicon Labs SI1142Proximity/Ambient Light Sensor with an I2C Interface. Also provided isbattery charging-supervision-disconnect circuitry 1236, and spring/RFantennas 1238. Also provided is a temperature sensor 1344 (risingperpendicular to the circuit board in the +z direction containing twoseparate temperature sensing elements at different distances from thecircuit board), and a PIR motion sensor 1242. Notably, even though thePROX/ALS and temperature sensors 1244 and PIR motion sensor 1246 arephysically located on the head unit circuit board 1940, all thesesensors are polled and controlled by the low-power backplatemicrocontroller on the backplate circuit board, to which they areelectrically connected. Optionally, in some implementations, the headunit circuit board includes a Bluetooth module 1248, and additionalcircuitry (not shown) which includes one or more oscillators,amplifiers, and/or any other support circuitry. In some implementations,the head unit circuit board includes one or more integrated circuitswhich include a combination of radios and transceivers. For example, insome implementations, the Wi-Fi module 1212 and the Bluetooth module1248 comprise a single chip, wherein the Wi-Fi module 1212 and theBluetooth module 1248 transmit and receive signals using a singleantenna 1238. Various implementations of transceivers (e.g., radios 940,radios 950) are described in greater detail with respect to FIGS. 9 and14-15G.

FIG. 12C illustrates a rear view of the backplate circuit board 1260,comprising a backplate processor/microcontroller 1262, such as a TexasInstruments MSP430F System-on-Chip Microcontroller that includes anon-board memory 1264. The backplate circuit board 1260 further comprisespower supply circuitry 1266, which includes power-stealing circuitry,and switch circuitry 1268 for each HVAC respective HVAC function. Foreach such function the switch circuitry 1268 includes an isolationtransformer 1270 and a back-to-back NFET package 1272. The use of FETsin the switching circuitry allows for “active power stealing”, i.e.,taking power during the HVAC “ON” cycle, by briefly diverting power fromthe HVAC relay circuit to the reservoir capacitors for a very smallinterval, such as 100 micro-seconds. This time is small enough not totrip the HVAC relay into the “off” state but is sufficient to charge upthe reservoir capacitors. The use of FETs allows for this fast switchingtime (100 micro-seconds), which would be difficult to achieve usingrelays (which stay on for tens of milliseconds). Also, such relays wouldreadily degrade doing this kind of fast switching, and they would alsomake audible noise too. In contrast, the FETS operate with essentiallyno audible noise. Also provided is a combined temperature/humiditysensor module 1274, such as a Sensirion SHT21 module. The backplatemicrocontroller 1262 performs polling of the various sensors, sensingfor mechanical wire insertion at installation, alerting the head unitregarding current vs. setpoint temperature conditions and actuating theswitches accordingly, and other functions such as looking forappropriate signal on the inserted wire at installation.

In accordance with the teachings of the commonly assigned U.S. Ser. No.13/269,501, supra, the commonly assigned U.S. Ser. No. 13/275,307,supra, and others of the commonly assigned incorporated applications,the smart thermostat 102 (FIG. 1) represents an advanced, multi-sensing,microprocessor-controlled intelligent or “learning” thermostat thatprovides a rich combination of processing capabilities, intuitive andvisually pleasing user interfaces, network connectivity, andenergy-saving capabilities (including the presently describedauto-away/auto-arrival algorithms) while at the same time not requiringa so-called “C-wire” from the HVAC system or line power from a householdwall plug, even though such advanced functionalities can require agreater instantaneous power draw than a “power-stealing” option (i.e.,extracting smaller amounts of electrical power from one or more HVACcall relays) can safely provide. By way of example, the head unitmicroprocessor 1202 can draw on the order of 250 mW when awake andprocessing, and an LCD module (not shown) can draw on the order of 250mW when active. Moreover, the Wi-Fi module 1212 can draw 250 mW whenactive, and needs to be active on a consistent basis such as at aconsistent 2% duty cycle in common scenarios. However, in order to avoidfalsely tripping the HVAC relays for a large number of commercially usedHVAC systems, power-stealing circuitry is often limited to powerproviding capacities on the order of 100 mW-200 mW, which would not beenough to supply the needed power for many common scenarios.

The smart thermostat 102 resolves such issues at least by virtue of theuse of a rechargeable battery (or equivalently capable onboard powerstorage medium) that will recharge during time intervals in which thehardware power usage is less than what power stealing can safelyprovide, and that will discharge to provide the needed extra electricalpower during time intervals in which the hardware power usage is greaterthan what power stealing can safely provide. In order to operate in abattery-conscious manner that promotes reduced power usage and extendedservice life of the rechargeable battery, the thermostat 1800 isprovided with both (i) a relatively powerful and relativelypower-intensive first processor (such as a Texas Instruments AM3703microprocessor) that is capable of quickly performing more complexfunctions such as driving a visually pleasing user interface display andperforming various mathematical learning computations, and (ii) arelatively less powerful and less power-intensive second processor (suchas a Texas Instruments MSP430 microcontroller) for performing lessintensive tasks, including driving and controlling the occupancysensors. To conserve valuable power, the first processor is maintainedin a “sleep” state for extended periods of time and is “woken up” onlyfor occasions in which its capabilities are needed, whereas the secondprocessor is kept on more or less continuously (although preferablyslowing down or disabling certain internal clocks for brief periodicintervals to conserve power) to perform its relatively low-power tasks.The first and second processors are mutually configured such that thesecond processor can “wake” the first processor on the occurrence ofcertain events, which can be termed “wake-on” facilities. These wake-onfacilities can be turned on and turned off as part of differentfunctional and/or power-saving goals to be achieved. For example, a“wake-on-PROX” facility can be provided by which the second processor,when detecting a user's hand approaching the thermostat dial by virtueof an active proximity sensor (PROX, such as provided by a Silicon LabsSI1142 Proximity/Ambient Light Sensor with I2C Interface), will “wakeup” the first processor so that it can provide a visual display to theapproaching user and be ready to respond more rapidly when their handtouches the dial. As another example, a “wake-on-PIR” facility can beprovided by which the second processor will wake up the first processorwhen detecting motion somewhere in the general vicinity of thethermostat by virtue of a passive infrared motion sensor (PIR, such asprovided by a PerkinElmer DigiPyro PYD 1998 dual element pyrodetector).Notably, wake-on-PIR is not synonymous with auto-arrival, as there wouldneed to be N consecutive buckets of sensed PIR activity to invokeauto-arrival, whereas only a single sufficient motion event can triggera wake-on-PIR wake-up.

FIGS. 13A-13D illustrate various views of a smart hazard detector (e.g.,smart hazard detector 104, FIG. 1) that may be used as part of a smarthome environment 100, as previously described.

Specifically, FIG. 13A illustrates an assembled view of the smart hazarddetector 104. FIG. 13A shows the mounting plate 1324, front casing 1326,and cover plate 1328 in an assembled configuration with the variousother components contained within an interior space of smart hazarddetector 104. These figures also show the plurality of holes or openingsof cover plate 1328 forming a visually pleasing design that is viewableby occupant of a room within which the smart hazard detector 104 ismounted. The lens button 1332 is shown attached to the smart hazarddetector 104 so as to be centrally positioned with respect to coverplate 1328. As briefly described, light ring 1342 may be used to providea halo appearance of light around and behind lens button 1332. Theassembled smart hazard detector 104 provides a compact yetmultifunctional device.

FIG. 13B illustrates an exploded perspective views of the smart hazarddetector 104. As shown in FIG. 13B, the smart hazard detector 104includes a mounting plate 1324 that may be attached to a wall of thebuilding or structure to secure the smart hazard detector 104 thereto.Smart hazard detector 104 also includes a back plate 1330 that may bemounted to the mounting plate 1324 and a front casing 1326 that may becoupled with or otherwise secured to back plate 1330 to define a housinghaving an interior region within which components of the smart hazarddetector 104 are contained. A circuit board 1300 may be coupled with orattached to back plate 1330. Various components may be mounted oncircuit board 1300. For example, a smoke chamber 1334 may be coupledwith or mounted on circuit board 1300 and configured to detect thepresence of smoke. In one embodiment, smoke chamber 1334 may bemid-mounted relative to circuit board 1300 so that air may flow intosmoke chamber 1334 from a position above circuit board 1300 and belowcircuit board 1300. A speaker 1336 and alarm device (not number) mayalso be mounted on circuit board 1300 to audibly warn an occupant of apotential fire danger when the presence of smoke is detected via smokechamber 1334. Other components, such as a motion sensor, carbon monoxidesensor, microprocessor, and the like may likewise be mounted on circuitboard 1300 as described herein.

In one embodiment, a protective plate 1338 may be attached to orotherwise coupled with circuit board 1300 to provide a visually pleasingappearance to the inner components of smart hazard detector 104 and/orto funnel or direct airflow to smoke chamber 1334. For example, when auser views the internal components of smart hazard detector 104, such asthrough vents in back plate 1330, protective plate 1338 may provide theappearance of a relatively smooth surface and otherwise hide thecomponents or circuitry of circuit board 1300. Protective plate 1338 maylikewise function to direct a flow of air from the vents of back plate1330 toward smoke chamber 1334 so as to facilitate air flow into and outof smoke chamber 1334.

Smart hazard detector 104 may also include a battery pack 1340 that isconfigured to provide power to the various components of smart hazarddetector 104 when smart hazard detector 104 is not coupled with anexternal power source, such as a 120 V power source of the home orstructure. In some embodiments, a cover plate 1328 may be coupled withthe front casing 1326 to provide a visually pleasing appearance to smarthazard detector 104 and/or for other functional purposes. In a specificembodiment, cover plate 1328 may include a plurality of holes oropenings that allow one or more sensors coupled with circuit board 1300to view or see through a surface of cover plate 1328 so as to senseobjects external to smart hazard detector 104. The plurality of openingsof cover plate 1328 may be arranged to provide a visually pleasingappearance when viewed by occupants of the home or structure. In oneembodiment, the plurality of openings of cover plate 1328 may bearranged according to a repeating pattern, such as a Fibonacci or othersequence.

A lens button 1332 may be coupled with or otherwise mounted to coverplate 1328. Lens button 1332 may allow one or more sensors to viewthrough the lens button 1332 for various purposes. For example, in oneembodiment a passive IR sensor (not shown) may be positioned behind thelens button 1332 and configured to view through the lens button 1332 todetect the presence of an occupant or occupants within the home orstructure. In some embodiments, lens button 1332 may also function as abutton that is pressable by a user to input various commands to smarthazard detector 104, such as to shut off an alarm that is triggered inresponse to a false or otherwise harmless condition. Positioned distallybehind lens button 1332 may be a light ring 1342 that is configured toreceive light, such as from an LED, and disperse the light within ring1342 to provide a desired visual appearance, such as a halo behind lensbutton 1332. Positioned distally behind light ring 1342 may be aflexible circuit board 1344 that includes one or more electricalcomponents, such as a passive IR sensor (hereinafter PIR sensor), LEDs,and the like. Flexible circuit board 1344 (hereinafter flex ring 1344)may be electrically coupled with circuit board 1300 to communicateand/or receive instructions from one or more microprocessors mounted oncircuit board (not shown) during operation of smart hazard detector 104.

Referring now to FIGS. 13C and 13D, illustrated are front and rearperspective views of a circuit board of a smart hazard detector (e.g.,smart hazard detector 104, FIG. 1). Circuit board 1300 includes a mainbody 1302 having a front side or surface and a rear side or surface. Asdescribed herein, various electrical components are mounted on circuitboard 1300. In some embodiments, these components may be mounted on thefront surface of circuit board 1300, on the rear surface of circuitboard 1300 opposite the front surface, or on both surfaces of thecircuit board 1300. For example, in a specific embodiment one or moremicroprocessors and/or other processor related components may be mountedon the rear surface of circuit board 1300 facing a protective platewhile one or more functional components (e.g. an alarm device, COdetector, speaker, motion sensors, Wi-Fi device, Zigbee device,Bluetooth device, and the like) are mounted on a front surface ofcircuit board 1300 facing a room of the home or structure in which thesmart hazard detector 104 is positioned. Other components may bemid-mounted relative to circuit board 1300 so that opposing surfaces arepositioned on opposing sides of the circuit board 1300 as describedherein. In some implementations, the circuit board 1300 includes one ormore integrated circuits which include a combination of radios andtransceivers. For example, in some implementations, a Wi-Fi device and aBluetooth device of the smart hazard detector 104 comprise a singlechip, wherein the Wi-Fi device and the Bluetooth device transmit andreceive signals using a single antenna. Various implementations oftransceivers (e.g., radios 940, radios 950) are described in greaterdetail with respect to FIGS. 9 and 14-15G.

As shown in FIG. 13C, in a specific embodiment the front surface ofcircuit board 1300 may include a CO detector 1304 that is configured todetect presence of carbon monoxide gas and trigger an alarm device 1306if the carbon monoxide gas levels are determined to be too high. Thealarm device 1306 (which can be a piezoelectric buzzer having anintentionally shrill or jarring sound) may likewise be mounted on thefront surface of circuit board 1300 so as to face an occupant of theroom in which the smart hazard detector 104 is positioned to alarm theoccupant of a potential danger. Alarm device 1306 may be configured toproduce one or more sounds or signals to alert the occupant of thepotential danger. The front surface may further include an area 1308 inwhich a speaker (not shown) is positioned. The Speaker may be configuredto provide audible warnings or messages to the occupant of the room. Forexample, the speaker may alert the occupant of a potential danger andinstruct the occupant to exit the room. In some embodiments, the speakermay provide specific instructions to the occupant, such as an exit routeto use when exiting the room and/or home or structure. Other messagesmay likewise be communicated to the occupant, such as to alert theoccupant that the batteries are low, that CO levels are relatively highin the room, that the smart hazard detector 104 needs periodic cleaning,or alert the occupant of any other abnormalities or issues related tohazard detector 104 or components thereof.

Circuit board 1300 may also include one or more motion sensors mountedon the front surface thereof. The motion sensors may be used todetermine the presence of an individual within a room or surroundingarea of the smart hazard detector 104. This information may be used tochange the functionality of the smart hazard detector 104 and/or one ormore other devices connected in a common network as describedpreviously. For example, this information may be relayed to a smartthermostat to inform the thermostat that occupants of the home orstructure are present so that the smart thermostat may condition thehome or structure according to one or more learned or programmedsettings. The smart hazard detector 104 may likewise use thisinformation for one or more purposes, such as to quiet the alarm device(e.g. gesture hush) as described herein or for various other reasons.

In one embodiment, a first ultrasonic sensor 1320 and a secondultrasonic sensor 1322 may be mounted on the front surface of circuitboard 1300. The two ultrasonic sensors, 1320 and 1322, may be offsetaxially so as to point in slightly different directions. In thisorientation, each ultrasonic sensor may be used to detect motion of anindividual based on an orientation of the smart hazard detector 104relative to the room and/or occupant. Detecting the motion of theindividual may be used to quiet the alarm device as described herein(i.e., gesture hush) or for any other reason. In one embodiment, an axisof the first ultrasonic sensor 1320 may be oriented substantiallyoutward relative to the smart hazard detector 104 while an axis of thesecond ultrasonic sensor 1322 is oriented an angle relative to the axisof the first ultrasonic sensor 1320. The first ultrasonic sensor 1320may sense motion of an individual when the smart hazard detector 104 ismounted on a ceiling of the home or structure. Because the firstultrasonic sensor 1320 is oriented substantially outward relative to thesmart hazard detector 104, the first ultrasonic sensor 1320 essentiallylooks straight down on individuals beneath the smart hazard detector104. The second ultrasonic sensor 1322 may similarly sense motion of theindividual when the smart hazard detector 104 is mounted on a wall ofthe home or structure. Because the second ultrasonic sensor 1322 isoriented at an angle relative to the first ultrasonic sensor 1320 andthe smart hazard detector 104, the second ultrasonic sensor essentiallylooks downward toward the floor when the smart hazard detector 104 ismounted on a wall of the home or structure, rather than looking directlyoutward as the first ultrasonic sensor 1320. In one embodiment, theangular offset of the two ultrasonic sensors may be approximately 30° orany other desired value.

In another embodiment, the two ultrasonic sensors, 1320 and 1322, may bereplaced by a single ultrasonic sensor that is configured to rotatewithin the smart hazard detector 104 so that the single ultrasonicsensor is capable of looking straight outward similar to the firstultrasonic sensor 1320 or capable of looking downward similar to thesecond ultrasonic sensor 1322. The single ultrasonic sensor may becoupled to circuit board 1300 via a hinge that allows the ultrasonicsensor to rotate based on the orientation of the smart hazard detector104. For example, when the smart hazard detector 104 is mounted to aceiling of the home or structure, gravity may orient the ultrasonicsensor so as to look straight downward; whereas when the smart hazarddetector 104 is coupled to a wall of the home or structure, gravity maycause the ultrasonic sensor to rotate via the hinge and look downwardtoward a floor and relative to the smart hazard detector 104. In anotherembodiment, a motor may be coupled with the single ultrasonic sensor soas to rotate the ultrasonic sensor based on the orientation of the smarthazard detector 104. In this manner, the ultrasonic sensor may alwayspoint in a direction that is likely to detect motion of an individualwithin the room or space surrounding the smart hazard detector 104. Inyet another embodiment, the single ultrasonic sensor may have a widefield of view that is able to substantially accommodate both mountingpositions of the two ultrasonic sensors, 1320 and 1322.

As shown in FIGS. 13C and 13D, body 1310 of circuit board 1300 alsoincludes a substantially centrally located aperture 1312 through which asmoke chamber is inserted so as to mid-mount the smoke chamber relativeto the circuit board 1300. Aperture 1312 may also include a pair ofnotches 1314 through which wires are inserted to electrically couple thesmoke chamber with circuit board 1300. As previously described,mid-mounting of the smoke chamber through an aperture 1312 allows smokeand air to enter the smoke chamber from both the front surface or sideof circuit board 1300 and the rear surface or side of circuit board1300. Various aspects of the electrical components on the circuit board1300 are now described, the positions thereon of many of which will beapparent to the skilled reader in view of the descriptions herein andFIGS. 13C and 13D. Included on the circuit board 1300 can be severalcomponents, including a system processor, relatively high-power wirelesscommunications circuitry and antenna, relatively low-power wirelesscommunications circuitry and antenna, non-volatile memory, audiospeaker, one or more interface sensors, a safety processor, safetysensors, alarm device 1306, a power source, and powering circuitry. Thecomponents are operative to provide failsafe safety detection featuresand user interface features using circuit topology and power budgetingmethods that minimize power consumption. According to one preferredembodiment, a bifurcated or hybrid processor circuit topology is usedfor handling the various features of the smart hazard detector 104,wherein the safety processor is a relatively small, relatively leanprocessor that is dedicated to core safety sensor governance and corealarming functionality as would be provided on a conventional smoke/COalarm, and wherein the system processor is a relatively larger,relatively higher-powered processor that is dedicated to more advancedfeatures such as cloud communications, user interface features,occupancy and other advanced environmental tracking features, and moregenerally any other task that would not be considered a “core” or“conventional” safety sensing and alarming task.

By way of example and not by way of limitation, the safety processor maybe a Freescale KL15 microcontroller, while the system processor may be aFreescale K60 microcontroller. Preferably, the safety processor isprogrammed and configured such that it is capable of operating andperforming its core safety-related duties regardless of the status orstate of the system processor. Thus, for example, even if the systemprocessor is not available or is otherwise incapable of performing anyfunctions, the safety processor will continue to perform its coresafety-related tasks such that the smart hazard detector 104 still meetsall industry and/or government safety standards that are required forthe smoke, CO, and/or other safety-related monitoring for which thesmart hazard detector 104 is offered (provided, of course, that there issufficient electrical power available for the safety processor tooperate). The system processor, on the other hand, performs what mightbe called “optional” or “advanced” functions that are overlaid onto thefunctionality of the safety processor, where “optional” or “advanced”refers to tasks that are not specifically required for compliance withindustry and/or governmental safety standards. Thus, although the systemprocessor is designed to interoperate with the safety processor in amanner that can improve the overall performance, feature set, and/orfunctionality of the smart hazard detector 104, its operation is notrequired in order for the smart hazard detector 104 to meet coresafety-related industry and/or government safety standards. Beinggenerally a larger and more capable processor than the safety processor,the system processor will generally consumes more power than the safetyprocessor when both are active.

Similarly, when both processors are inactive, the system processor willstill consume more power than the safety processor. The system processorcan be operative to process user interface features and monitorinterface sensors (such as occupancy sensors, audio sensors, cameras,etc., which are not directly related to core safety sensing). Forexample, the system processor can direct wireless data traffic on bothhigh and low power wireless communications circuitry, accessnon-volatile memory, communicate with the safety processor, and causeaudio to be emitted from the speaker. As another example, the systemprocessor can monitor interface sensors to determine whether any actionsneed to be taken (e.g., shut off a blaring alarm in response to a userdetected action to hush the alarm). The safety processor can beoperative to handle core safety related tasks of the smart hazarddetector 104. The safety processor can poll safety sensors (e.g., smoke,CO) and activate alarm device 1306 when one or more of safety sensorsindicate a hazard event is detected. The safety processor can operateindependently of the system processor and can activate the alarm device1306 regardless of what state the system processor is in. For example,if the system processor is performing an active function (e.g.,performing a Wi-Fi update) or is shut down due to power constraints, thesafety processor can still activate the alarm device 1306 when a hazardevent is detected.

In some embodiments, the software running on the safety processor may bepermanently fixed and may never be updated via a software or firmwareupdate after the smart hazard detector 104 leaves the factory. Comparedto the system processor, the safety processor is a less power consumingprocessor. Using the safety processor to monitor the safety sensors, asopposed to using the system processor to do this, can yield powersavings because safety processor may be constantly monitoring the safetysensors. If the system processor were to constantly monitor the safetysensors, power savings may not be realized. In addition to the powersavings realized by using safety processor for monitoring the safetysensors, bifurcating the processors can also ensure that the safetyfeatures of the smart hazard detector 104 always work, regardless ofwhether the higher level user interface works. The relatively high powerwireless communications circuitry can be, for example, a Wi-Fi modulecapable of communicating according to any of the 802.11 protocols.

By way of example, the relatively high power wireless communicationscircuitry may be implemented using a Broadcom BCM43362 Wi-Fi module. Therelatively low power wireless communications circuitry can be a lowpower Wireless Personal Area Network (6LoWPAN) module or a ZigBee modulecapable of communicating according to an IEEE 802.15.4 protocol. Forexample, in one embodiment, the relatively low power wirelesscommunications circuitry may be implemented using an Ember EM357 6LoWPANmodule. The non-volatile memory can be any suitable permanent memorystorage such as, for example, NAND Flash, a hard disk drive, NOR, ROM,or phase change memory. In one embodiment, the non-volatile memory canstore audio clips that can be played back using the speaker 1336. Theaudio clips can include installation instructions or warning in one ormore languages. The interface sensors can includes sensors that aremonitored by system processor, while the safety sensors can includesensors that are monitored by the safety processor. Sensors can bemounted to a printed circuit board, a flexible printed circuit board, ahousing of a system, or a combination thereof.

The interface sensors can include, for example, an ambient light sensor(ALS) (such as can be implemented using a discrete photodiode), apassive infrared (PIR) motion sensor (such as can be implemented usingan Excelitas PYQ1348 module), and one or more ultrasonic sensors (suchas can be implemented using one or more Manorshi MS-P1640H12TR modules).The safety sensors can include, for example, the smoke detection chamber1334 (which can employ, for example, an Excelitas IR module), the COdetection module 1304 (which can employ, for example, a Figaro TGS5342sensor), and a temperature and humidity sensor (which can employ, forexample, a Sensirion SHT20 module). The power source can supply power toenable operation of the smart hazard detector and can include anysuitable source of energy. Embodiments discussed herein can include ACline powered, battery powered, a combination of AC line powered with abattery backup, and externally supplied DC power (e.g., USB suppliedpower). Embodiments that use AC line power, AC line power with batterybackup, or externally supplied DC power may be subject to differentpower conservation constraints than battery only embodiments.

Preferably, battery-only powered embodiments are designed to managepower consumption of its finite energy supply such that smart hazarddetector 104 operates for a minimum period of time of at least seven(7), eight (8), nine (9), or ten (10) years. Line powered embodimentsare not as constrained. Line powered with battery backup embodiments mayemploy power conservation methods to prolong the life of the backupbattery. In battery-only embodiments, the power source can include oneor more batteries. The batteries can be constructed from differentcompositions (e.g., alkaline or lithium iron disulfide) and differentend-user configurations (e.g., permanent, user replaceable, or non-userreplaceable) can be used. In one embodiment, six cells of Li—FeS2 can bearranged in two stacks of three. Such an arrangement can yield about27000 mWh of total available power for the smart hazard detector 104.

FIG. 14 illustrates a block diagram of a communications module 942 of asmart device utilizing bypass circuitry, in accordance with someimplementations. FIG. 14 illustrates a communications module 942 of asmart device 204 (e.g., FIG. 9), in accordance with any of theimplementations disclosed in FIGS. 1-9 (e.g., devices 102, 104, 106,108, 110, 112, 114, 116, 118, 120, and/or 122, FIG. 1, such as a camera118, a smart hazard detector 104, a smart thermostat 102, etc.).

In some implementations, the communications module 942 includes one ormore radios 940, radios 950, a front end module 1400, and antennas 1402.In some implementations, the one or more radios 940 and radios 950 arecommunicably connected, and each have respective antennas 1402 throughwhich respective signals are transmitted and received. As an example,the communications module 942 of a camera 118 includes a firsttransceiver for transmitting video data (e.g., Wi-Fi, radios 950), andadditionally includes a second transceiver for transmitting andreceiving packets from other smart devices in a smart home environment(e.g., Zigbee, radios 940). Optionally, a combined transceiver isconfigured for transmitting and receiving data in accordance with morethan one communications protocol (e.g., radio 950 configure for Wi-Fiand Bluetooth LE). Components of the communications module 942 (e.g.,radios 940, radios 950) are described in greater detail with regards toFIG. 9.

The front end module 1400 of the communications module 942 includes avariety of circuit elements for manipulating (e.g., amplifying) signalsreceived and transmitted by the radios 940. In particular, the front endmodule 1400 includes switches 1404 for coupling the radios 940 and theantenna 1402 by selectively using an amplifier (e.g., amplifier 1406-1and a low noise amplifier 1406-2) or bypass line 1408. Whether the frontend module 1400 couples the radios 940 and the antenna 1402 by the lownoise amplifier 1406-2 or the bypass line 1408 depends on whether theradio 950 is active and transmitting signals using the second antenna1402-2. Although not illustrated, other implementations of the front endmodule 1400 may include additional circuit elements, including one ormore additional switches, amplifiers, transistors, and/or anycombination of active or passive elements. A combination of circuitelements may be used in the front end module 1400, for example, tomodify the sensitivity of the communications module 942 and signalstransmitted and/or received through the radios 940.

As described previously, poor signal isolation typically results fromthe close physical placement of antennas 1402. In particular, devicecomponents risk damage in the event that the signal power oftransmitting antennas in a transmission chain nearby (e.g., antenna1402-2 for Wi-Fi transmissions) exceeds the maximum input power ofcomponents in the receiving chain (e.g., 802.15.4 receiving chain formedby radio(s) 940 and antenna 1402-1).

One method for enabling and enhancing coexistence of transceiver devices(e.g., radios 940, radios 950) includes the use of a bypass line 1408 ina front end module 1400. In particular, by using the switches 1404 toautomatically and selectively enable the bypass line 1408 when the radio950 (e.g., Wi-Fi) is “on” and transmitting signals through the antenna1402-2 (e.g., radios 950 signals to the front end module 1400 throughconnection 1410 that it is “on” and transmitting), transmissionsreceived through the antenna 1402-1 do not pass through the low noiseamplifier 1406-2, and instead pass through the bypass line 1408 to theradios 940. Consequently, the effective maximum input power that can betolerated by the front end module 1400 may be increased (i.e., the frontend module 1400 has a larger input power threshold when the bypass line1408 is used to couple the radio 940 and the antenna 1402-1), asdetermined by characteristics of the bypass line 1408, rather than thelow noise amplifier 1406-2. When the radio 950 is “off,” the switches1404 operate to couple the radios 940 and the antenna 1402-1 with thelow noise amplifier 1406-2 in the receiver pathway. Thus, with respectto receiver chain sensitivity, the front end module 1400 has a higherreceiver sensitivity when the low noise amplifier 1406-2 is used tocouple the radio 940 and the antenna 1402-1. Given the selectiveoperation of the low noise amplifier 1406-2 based on the activity of theradio 950, the risk of damage to the low noise amplifier 1406-2 isavoided, while still achieving improved sensitivity through the use ofthe low noise amplifier 1406-2. Therefore, the front end module 1400 isconfigured to couple the antenna 1402-1 to the radio 940 via the bypassline 1408 when the radio(s) 950 is active and transmitting signals usingthe antenna 1402-2 such that a signal received via the antenna 1402-1 isnot amplified by the amplifier 1406-2 prior to being passed to the radio940. The front end module 1400 is further configured to couple theantenna 1402-1 to the radio 940 via the amplifier 1406-2 when theradio(s) 950 is not transmitting signals using the antenna 1402-2 suchthat a signal received via the antenna 1402-1 is amplified by theamplifier 1406-2 prior to being passed to the radio 940. Methods ofcoexistence using the bypass circuitry in FIG. 14 is described ingreater detail with respect to FIG. 22.

FIGS. 15A-15L illustrate a coexistence scheme for a smart device havingmultiple radios in smart home environment 100, in accordance with someimplementations.

As illustrated in FIG. 15A, a smart device 204 (e.g., a camera 118)transmits data to and receives data from other devices in proximity(e.g., smart hazard detector 104, camera 118, smart thermostat 102).Simultaneously, data (e.g., live video stream recorded by the camera118) is transmitted to and from a remote server system over a network(e.g., a smart home provider server system 164, over the network 162through a network interface 160). In some implementations, the variousdevices in the smart home environment 100 are also communicablyconnected and may therefore transmit/receive data from one another. Thespecific smart devices illustrated and described in FIG. 15A are merelyexamples, and other implementations include various combinations ofsmart devices (not illustrated).

In some implementations, a camera 118 (or any smart device 204 thatprovides high bandwidth output data) needs to transmit one more videostreams at different resolutions (e.g., 180p, 780p and 1080p) to theserver system 164 for additional processing, storage, and/or sharingwith authorized users. In some situations, as when the video stream is alive, high definition (e.g., 780p or 1080p) video stream, this requiresthe camera 118 to maintain a low latency, high bandwidth connection tothe server system 164 through the network interface 160 for asubstantial period of time (e.g., from a few minutes to hours). This isaccomplished in some implementations by the camera 118 employing a Wi-Ficonnection provided by the network 162 to connect to the server system164 to transmit video streams. At the same time, the camera 118 needs tobe responsive to high priority alerts from other smart devices 204 sothese alerts can be processed locally (e.g., used to change system statein the camera 118, transmitted to a hub device 180 for integrationprocessing in view of other system alerts and status information,relayed to other smart home devices 204, or transmitted to clientdevices 504 that are configured to issue alerts directed to authorizedusers) and/or transmitted to the server system 164. In someimplementations, these alerts are issued via Bluetooth or IEEE802.11.15.4 signals by radios in other smart devices 204 (such as asmart hazard detector 304) and are received by corresponding radios inthe camera 118 (or any comparable smart device 204). These alerts aretypically of short duration and low bandwith in contrast to streamingvideo, which is long duration and high bandwidth. In someimplementations, these alerts need to be retransmitted to other smartdevices 204 by the corresponding Bluetooth or IEEE 802.11.15.4 radios inthe camera 118 (or any comparable smart device 204), which operate atthe same frequency as the Wi-Fi radio (e.g., 2.4 GHz). This requires thecamera 118 to prioritize use of the radios and antennas such that highpriority transmissions received from other smart devices 204 (e.g.,smoke or CO alerts) are transmitted with minimal latency, while duringnormal operation (e.g., when there are no incoming alerts from othersmart devices 204), video streaming is enabled with high efficiencythrough the Wi-Fi radio. Devices with multiple radios (e.g., Wi-Fi,Bluetooth, and 802.11.15.4) may be utilized in a number of additionalways. In some embodiments, for example, one or more radios of a devicemay be used for secure device provisioning (e.g., via Bluetooth).Additionally, as described above, one or more radios may also be usedfor low-power communications (e.g., in devices not connected to apersistent power source).

Any of the operations described above in which multiple radios areutilized require a co-existence strategy, described herein, that managesthe use by multiple radios (e.g., 2 or more) of one or more antennaswith poor isolation from each other to transmit without interferencesignals at the same frequency or frequencies that would otherwiseinterfere.

In different implementations, a smart device 204 can be any sort of homeautomation device that employs multiple radios for a variety ofpurposes, including purposes similar to those described herein (e.g., aWi-Fi radio to stream data to a cloud service or with a local network, aBluetooth radio for configuration purposes, and an IEEE 802.11.15.4 15radio to enable communications with other home automation devices insmart devices in a smart home environment to, or purposes that differ inone or more ways from those purposes (e.g., without limitation, a Wi-Firadio used to exchange data, alerts, and/or control commands with,and/or monitor communication status of, other smart home automationdevices, a Bluetooth radio used to exchange data, alerts, and/or controlcommands with, and/or monitor communication status of, other smart homeautomation devices; and an IEEE 802.11.15.4 radio used to transmitremote control commands and occupant presence information from one homeautomation device to another). For example, the smart device 204 can bea smart/connected appliance, such as a refrigerator, washing machine,dryer, or dishwasher; a home entertainment device, such as a television,digital video recorder, audio/visual receiver, connected speaker, ormedia projector; a home networking device, such as a network router,switch or network attached storage; a home security/access device, suchas a connected door lock, garage door controller, or doorbell withintegrated security camera or hazard detector; indoor and/or outdoorhome lighting devices; landscape irrigation devices and controllers;automated home window coverings and/or skylights; and heating andcooling systems.

Each of the home automation devices 204 has specific features (e.g., enduser features, operating features and/or network/collaboration features)based upon its type and purpose, and includes electronic andelectromechanical components that can be controlled and/or automated tofurther the purposes/uses of a home automation environment and/or of therespective automation device. For example, a particular smartrefrigerator with a rich set of connected features (i.e., featurescontrollable via various network connections to other smart home devicesand/or to applications running on end user devices—such as a smartphones, tablets, laptops or desktop) might have a compressor, ice cubemaker, internal and exterior lighting, freezer section, refrigeratorsection, external display panel, processor, audio recorder/microphone,video camera, memory, proximity sensor and three different radios, allof which support one or more of inter-device communications and/or datastreaming. Given a refrigerator configured as described above, in someimplementations, temperature of the freezer and refrigerator sections,ice maker operation, etc. can be controlled over Wi-Fi, Bluetooth orIEEE 802.11.15.4 connections, refrigerator performance data and recordedand/or live audio and video can be sent over the Wi-Fi connection, andstatus and presence messages and alerts can be exchanged with other homeautomation devices using IEEE 802.11.15.4 connections. As anotherexample, given a landscape irrigation controller with Wi-Fi, Bluetoothand IEEE 802.11.15.4 radios, the controller can transmit irrigationcommands (e.g., ON and OFF) consistent with irrigation programs tooutdoor sprinklers using IEEE 802.11.15.4 connections, obtain weatherinformation (such as temperature and predicted precipitation from theInternet and/or local smart home automation devices—e.g., an outdoormoisture detector—via the Wi-Fi connection, and can accept operating andconfiguration commands from a smart phone running an correspondingirrigation app using Bluetooth or Wi-Fi connections. In these exampleimplementations and other similar implementations, the multiple radiosand their respective antennas are located in accordance with antennaplacement principles described herein and the multiple radios areconfigured to co-exist (i.e., cooperatively transmit and receive overtheir associated antennas) using co-existence principles and signalsdescribed herein.

As shown in FIG. 15A, some implementations of a communications module942 include one or more radios 940, radios 950, antennas 1402, anoptional front end module 1400 (as described in FIG. 14), and one ormore control lines 1500 which transmit signals between the one or moreradios 940 and radios 950 (e.g., RADIO_PRI on control line 1500-1,RADIO_REQ on control line 1500-2, and WIFI_GRANT on control line1500-3). Various components of the communications module 942 aredescribed in greater detail with respect to FIGS. 9 and 14.

In some implementations, the control lines 1500 are used to transmitcontrol signals between one or more radios 940 and radios 950 to managethe operation of transceiver devices in accordance with a coexistencescheme. In particular, as described in greater detail below, controlsignals are transmitted as a means for indicating and determining apriority of signals being transmitted by the one or more radios 940 andradios 950. A transceiver determined to have a lower priority yields toa higher priority transceiver by suspending transmissions for a durationof time as the higher priority transceiver completestransmitting/receiving data, thus lessening or altogether avoiding thenegative effects of poor isolation resulting from transceiver devicesoperating simultaneously. As an example, when the RADIO_PRI (i.e.,request for transmission priority) and RADIO_REQ (e.g., request fortransmission) control lines 1500-1 and 1500-2 are asserted by the radios940, the radio 950 yield to transmission requests by the radios 940 bysuspending its own transmissions while the radios 940 transmit/receivedata. Referring to the example in FIG. 15A, when the RADIO_PRI andRADIO_REQ control lines 1500-1 and 1500-2 are asserted, the radio 950 ofthe smart device 204 (e.g., Wi-Fi transceiver of a camera 118)momentarily suspend uploads of recorded video to the smart home providerserver system 164, while permitting the radios 940 (e.g., 802.15.4) totransmit critical packets received from a smart hazard detector 104 to asmart thermostat 102 by activating (or “asserting”) the WIFI_GRANTcontrol signal. As a result, interference and transmission collisionsare avoided between the transceiver devices, while reducing the risk ofdamaging hardware components (e.g., by exceeding device input powerthresholds) and failing to transmit critical data (e.g., emergency pingsfrom a smart hazard detectors 104).

In some implementations, one of the transceivers serves as a “master”device which receives requests for transmissions and moderatestransmissions between itself and requesting transceivers. In the exampleshown, the radio 950 (e.g., Wi-Fi transceiver) is the master, asindicated by the directions of the control lines 1500 (i.e., withrespect to the radio 950, WIFI_GRANT is an output, and RADIO_PRI andRADIO_REQ are inputs).

The radios 940 and/or the radios 950 may operate in station mode (i.e.,transceiver acts as a client that connects to an access point, such as arouter), Access Point (AP) mode (i.e., transceiver acts as an accesspoint through which other devices can connect and access other connecteddevices), and/or Ad-Hoc mode (e.g., mode in which network connecteddevices have equal status and may associate with any other networkdevice in range). Furthermore, radios 940 and/or the radios 950 mayoperate in a variety of power modes (e.g., full power mode, power savemode). In the example coexistence scheme of FIGS. 15A-15L, the radio 950(e.g., Wi-Fi) operates in station mode and full power mode. Furthermore,in the given example, the WIFI_GRANT control signal is kept activatedwhen the radio 950 is in power save mode.

Although the example illustrates the use of three control lines, otherimplementations may include additional control lines and control signalsfor determining a request priority of a transmitting device. Additionalcontrol lines and control signals may, for example, be used inimplementations which include two or more radios 940 or radios 950 in acombined device (e.g., a combined Bluetooth and 802.15.4 chip), suchthat the plurality of transceiver devices can separately arbitrate withthe master device.

Alternatively, in some implementations, two or more radios 940 or radios950 are integrated as a combined device (e.g., a combined Bluetooth andWi-Fi 802.11 chip), and a separate arbitration scheme may be implementedsuch that the two radios 940 or radios 950 arbitrate internally beforearbitrating with the other transceiver of the communications module 942.FIG. 15B illustrates an example of an internal arbitration schemebetween transceivers combined in a single device (e.g., Bluetooth andWi-Fi transceivers combined in a single device, shown by radios 950-1and 950-2, respectively). Using a switch 1404-3, for example, radios950-1 and 950-2 decide between each other (e.g., based on instructionsand logic in the firmware of radio 950-1 and/or 950-2) as to whichtransceiver will have control over the antenna 1402-2. Thus, the examplecoexistence scheme of FIG. 15A operates independently from, butsimultaneously with, any internal coexistence schemes implementedbetween radios 940 or radios 950 (e.g., coexistence scheme involving802.15.4 and Wi-Fi is independent from internal coexistence schemeinvolving Wi-Fi and Bluetooth).

While reference is made with respect to 802.15.4 and Wi-Fi, otherimplementations may include any combination of other transmissionprotocols described with respect to FIGS. 9 and 14.

FIG. 15C illustrates a table of example control signal assignments. Asdescribed above, the example coexistence scheme of FIGS. 15A-15L usesthree signals, RADIO_REQ (input), RADIO_PRI (input) and WIFI_GRANT(output). These control signals may be assigned to various physical pinsof the radios 940 and radio 950 (e.g., pins L6, L7, and L8).

Coexistence schemes may be configured and implemented with any signalpolarity (High-Active or Low-Active). In the example shown, the signalpolarity is assumed to be Low-Active. In some implementations, controlsignals and control lines 1500 are assigned to physical pins of thetransceivers, and are therefore handled by on-chip target firmware.Thus, control signals do not directly control the transceivers (e.g., tostop/resume Wi-Fi transmission), but rather operate through logicimplemented by device firmware.

The use of these control signals are configured such that the radio 940and radio 950 can support two modes of operation: a “normal” and“alarming” mode.

In the “normal” mode, the radio 940 (e.g., 802.15.4) operatesasynchronously. That is, the radio 940 can request transmission accessat any time. In this mode, the priority pin (e.g., RADIO_PRI) will notbe asserted. Furthermore, the radio 950 (e.g., Wi-Fi) is permitted(although not required) to complete existing packet transmissions beforegranting transmission requests to the radio 940 (i.e., assertingWIFI_GRANT).

In “alarming” mode (or “high priority” mode), the radio 940 (e.g.,802.15.4) requests access in a periodic fashion. As an example, theradio 940 requests for a 900 us transmission period every 4 ms. Thepriority control signal (e.g., RADIO_PRI) will be asserted during thisentire period and can be used by the radio 950 (e.g., Wi-Fi) to inferthe mode. In some implementations, in the alarming mode, the radio 940and the radio 950 operate synchronously. That is, transmissions from theradio 950 (e.g., Wi-Fi) are timed with the falling (or rising) edge ofthe RADIO_REQ control signal. By synchronously timing the assertion andde-assertion of the RADIO_REQ control signal, minimum timing guaranteescan be created with respect to transmission access for the radio 950.This is in contrast to “normal mode,” where a looser coupling existsbetween transmissions between radio(s) 940 and radio(s) 950, wheretransmission access is granted/denied in an ad hoc fashion.

Implementations of the various controls signals for supporting thesemodes of operation are described below.

In some implementations, the RADIO_REQ control signal (e.g., controlline 1500-2, FIG. 15A) is a transmission request signal from the radios940 (e.g., 802.15.4 transceiver). When the radio 950 (e.g., Wi-Fitransceiver) detects this signal, it attempts to suspend itstransmissions and simultaneously activates the WIFI_GRANT control signal(e.g., control line 1500-3, FIG. 15A), indicating that its transmissionhas stopped and that the radios may begin transmission (e.g., on ashared 2.4 GHz frequency band).

In some implementations, the RADIO_PRI control signal (e.g., controlline 1500-1, FIG. 15A) is signal from the radios 940 (e.g., 802.15.4)indicating an importance of the transmission request. Thus, if RADIO_PRIis active when RADIO_REQ is detected, the radio 950 (e.g., Wi-Fi) willtreat it as “high priority” request. Consequently, the radio 950attempts to shut down its transmissions as soon as possible, activatesthe WIFI_GRANT control signal, and does not revoke the WIFI_GRANTcontrol signal until RADIO_REQ is deactivated.

If RADIO_PRI is inactive when RADIO_REQ is detected, the radio 950 willtreat it as “regular priority” request. Thus, if an important operationby the radio 950 is in progress (e.g., scheduled beacon receive), theWIFI_GRANT control signal will not be activated until that operation iscompleted. Furthermore, if the WIFI_GRANT control signal is alreadyactivated when the RADIO_REQ control signal is also activated,WIFI_GRANT will be revoked (deactivated) if and when the radio 950 seeksto access to the radio.

The RADIO_PRI control signal is checked when the radio 950 (e.g., Wi-Fitransceiver) detects a change of the RADIO_REQ control signal (e.g.,activation/inactivation). The RADIO_PRI control signal level must beestablished a time T_PRI_SETUP before changing the RADIO_REQ controlsignal. When the RADIO_REQ control signal is still activated when theRADIO_PRI control signal is activated, it triggers an “alarming” mode tothe radio 950, forcing a “slotted” mode operation. The slotted mode isimplemented in order to respond rapidly during a RADIO_REQ interval inhigh priority mode (“alarming mode,” an example of which is describedwith respect to FIGS. 15K and 15L). In slotted mode, a TX RequestDescriptor is placed in the hardware queue only upon inactivation of theRADIO_REQ control signal. The transmission throughput of the radio 950(e.g., Wi-Fi) in slotted mode is limited to a single packet in everyRADIO_REQ interval. Thus, only a single Wi-Fi packet is sent every timewhen the RADIO_REQ control signal is inactivated. In someimplementations, when switching from alarming mode to normal mode, theRADIO_PRI must be inactivated when RADIO_REQ is inactivated. Assuming1440 Bytes/packet and a 4 ms RADIO_REQ interval, transmission throughputof the radio 950 under alarming mode is 2.7 Mbit/sec. In addition, Wi-Firetry limit is set to 3 in slotted mode, where default retry limit is15.

The WIFI_GRANT control signal is provided by the radio 950 (e.g.,Wi-Fi), which, when activated, indicates that the transmission activityof the radio 950 was ceased, and that the radios 940 (e.g., 802.15.4transceiver) may use the frequency band for transmission (e.g., 2.4 GHzband).

Furthermore, in order to achieve quick pause-resume of transmissions bya Wi-Fi transceiver, in some implementations 802.11n sub-frameaggregation is disabled. Furthermore, in some implementations, thenumber of TX Request Descriptors placed in the hardware transmissionqueue is limited to 1. As a result, the transmission throughput of theWi-Fi transceiver, for example, is reduced about 10 Mbps even whenconnected to an 802.11n access point.

In some implementations, a camera device (e.g., smart device 204 in FIG.15A, which is a camera) includes a first and second antenna (e.g.,antennas 1402-1 and 1402-2, respectively), and a first (e.g., radio950-1, FIG. 15B), second (e.g., radio 940, FIG. 15A), and thirdtransceiver (e.g., radio 950-2, FIG. 15B). The second transceiver iscoupled to the first antenna (e.g., radio 940 coupled to antenna1402-1), and the first and third transceivers are coupled to the secondantenna (e.g., radios 950-1 and 950-2 coupled to antenna 1402-2, FIG.15B). In some implementations, the first transceiver is configured totransmit and receive, over a first one of a plurality of distinctcommunication protocols, signals for configuring the camera device(e.g., Bluetooth Low Energy), the second transceiver is configured totransmit and receive, over a second one of the plurality of distinctcommunication protocols, signals comprising one or more of alerts,control signals and status information to and from the one or more smarthome devices (e.g., 802.15.4), and the third transceiver is configuredto transmit and receive, over a third one of the plurality of distinctcommunication protocols, data corresponding to video captured by thecamera device (e.g., Wi-Fi). In some implementations, the secondtransceiver and the first and/or third transceivers are coupled by aplurality of control lines for selectively granting or denyingtransmission access to the first, second, and third transceivers (e.g.,control lines 1500, FIG. 15A). In some implementations, the firsttransceiver and the third transceiver comprise a single combinedtransceiver (e.g., radio 950, which includes radio 950-1 and radio950-2, FIG. 15B), and the second transceiver is coupled to the singlecombined transceiver by the plurality of control lines (e.g., radio 940and radio 950 coupled by control lines 1500, FIG. 15A).

In some implementations, the plurality of control lines include a firstcontrol line for a priority control signal (e.g., RADIO_PRI on controlline 1500-1, FIG. 15A), a second control line for a radio requestcontrol signal (e.g., RADIO_REQ on control line 1500-2), and a thirdcontrol line for granting or denying transmission access to the secondtransceiver or the third transceiver (e.g., WIFI_GRANT on control line1500-3). Transmission access is granted or denied to the secondtransceiver or the third transceiver using the third control line inaccordance with detection of an activated or deactivated prioritycontrol signal, an activated or deactivated radio request controlsignal, and/or a transmission request by the third transceiver. In someimplementations, transmission access is granted to the secondtransceiver and denied to the third transceiver if an activated prioritycontrol signal is detected on the first control line and an activatedradio request control signal is detected on the second control line; ora deactivated priority control signal is detected on the first controlline and the activated radio request control signal is detected on thesecond control line, but the transmission request by the thirdtransceiver is not detected. In some implementations, transmissionaccess is denied to the second transceiver and granted to the thirdtransceiver if an activated priority control signal is detected on thefirst control line, a transmission request by the third transceiver isdetected, and a deactivated radio request control signal is detected onthe second control line; or a deactivated priority control signal isdetected on the first control line and the transmission request by thethird transceiver is detected. Granting and denying of transmissionaccess to the first transceiver, the second transceiver, and/or thethird transceiver is described in greater detail with respect to FIGS.23A-23F.

FIGS. 15D-15L illustrate various signal timing diagrams and timingcharts for various modes of operation in a coexistence scheme, inaccordance with some implementations. As stated previously, in theexamples shown and described with respect to FIG. 15D-15L, the signalpolarity of the control signals is Low-Active (i.e., control signal isconsidered “active” when low), although control signals may beconfigured in other implementations to have a High-Active polarity.Furthermore, the timing charts illustrated in FIGS. 15D-15L are merelyexamples of timing requirements (e.g., minimum/maximum requirements) foran example coexistence scheme, and in other implementations, thecommunications module 942 of a smart device (e.g., camera 118, smarthazard detector 104, smart thermostat 102, etc.), and components thereof(e.g., radios 940, radios 950), are configured to satisfy otherpredefined timing requirements.

In particular, FIGS. 15D and 15E illustrate a signal timing diagram andtiming chart for a normal mode of operation for a coexistence scheme, inaccordance with some implementations.

As shown in FIG. 15D, even if the RADIO_PRI control signal is activated,the WIFI_GRANT control signal is not asserted until the RADIO_REQcontrol signal is activated. As shown in the timing chart of FIG. 15E,T_PRI_SETUP is the setup time between asserting RADIO_PRI and assertingRADIO_REQ. Moreover, T_REQ_LATENCY is the latency between assertingRADIO_REQ and asserting WIFI_GRANT. The T_REQ_LATENCY time is defined byrequirements of the radios 940 (e.g., 802.15.4 radio requirement) andimplementation limitations of the radio 950 (e.g., Wi-Fi). In someimplementations, the T_REQ_LATENCY time is mainly general-purpose I/O(GPIO) interrupt latency plus the TX DMA stop latency (e.g., a maximumof 3.5 msec). The WIFI_GRANT control signal could be further delayed,however, for beacon protection (described in greater detail with respectto FIGS. 15H and 151).

Furthermore, as shown in FIG. 15D, when both the RADIO_PRI controlsignal and the RADIO_REQ are deactivated, the WIFI_GRANT is revoked. TheT_REVOKE_LATENCY time is the latency between de-asserting RADIO_REQ andde-asserting WIFI_GRANT.

Additional timing metrics include T_REQ_PERIOD, which is the length oftime for which the RADIO_REQ control signal is asserted. In someimplementations, T_REQ_PERIOD is defined from requirements of the radios940 (e.g., 802.15.4 radio requirement) and throughput/connectionstability of the radio 950 (e.g., Wi-Fi). Furthermore, T_REQ_INTERVAL isdefined as the interval of time between asserting the RADIO_REQ controlsignal.

FIGS. 15F and 15G illustrate a signal timing diagram and timing chartfor a mode of operation in a coexistence scheme in which a request grantis revoked based on predefined performance requirements, in accordancewith some implementations.

In particular, the signal timing diagram of FIG. 15F illustrates asignal timing diagram in which the WIFI_GRANT control signal is revokedin accordance with Quality of Service (QoS) requirements. In the exampleprovided, when RADIO_PRI is not asserted, WIFI_GRANT will be revokedwhen there is a high priority transmission request by the radio 950(e.g., Wi-Fi), even if the RADIO_REQ control line is still asserted. Insome implementations, a “High priority” transmission request isconsidered to be within an Access Category (AC) that is above BE (BestEffort), VI (Video) and/or VO (Voice), respectively. For example,management frames are considered to be the same priority as VO (Voice).

FIG. 15G illustrates a timing chart in which WIFI_GRANT is revoked inaccordance with QoS requirements. As the RADIO_PRI control signal isassumed to be de-asserted, this example pertains only to a non-prioritycoexistence request.

As shown in FIG. 15F, if a “high priority” transmission occurs,WIFI_GRANT will be revoked even if the RADIO_REQ control signal isasserted. The time T_REVOKE_LEAD_Q is defined as the lead period betweende-asserting the WIFI_GRANT and the “high priority” Wi-Fi transmission.Furthermore, the time T_WIFI_ACT is the duration of time of the highpriority Wi-Fi transmission.

When the high-priority transmission ceases, WIFI_GRANT is re-asserted,the amount of time between such occurrences being defined byT_REGRANT_LATENCY_Q.

Other timing metrics include T_GRANT_MIN_Q, which is the minimum amountof time for which WIFI_GRANT can be guaranteed to be asserted. In someimplementations, because transmission activity of the radio 950 (e.g.,Wi-Fi) is asynchronous to a request signal from the radios 940 (e.g.,802.15.4), a minimum WIFI_GRANT period (e.g., time T_GRANT_MIN_Q) is notguaranteed.

Furthermore, T_WIFI_IDLE is defined as the interval of time betweenhigh-priority transmission requests.

FIGS. 15H and 151 illustrate a signal timing diagram and timing chartfor a mode of operation for a coexistence scheme utilizing beaconprotection, in accordance with some implementations.

FIG. 15H illustrates a timing chart with beacon protection. WhenRADIO_PRI is not asserted, WIFI_GRANT will be revoked in order to avoidinterference with incoming beacons received by the radio 950 (e.g.,Wi-Fi beacons). As the RADIO_PRI control signal is assumed to bede-asserted, this example pertains only to a non-priority coexistencerequest.

As shown, if a beacon transmission occurs, WIFI_GRANT will be revokedeven if the RADIO_REQ control signal is asserted.

T_GRANT_MIN is defined as a minimum period of time for which WIFI_GRANTcan be guaranteed to be asserted before being revoked by a beacontransmission. T_REVOKE_LEAD is defined as a lead period betweenWIFI_GRANT being de-asserted and the time at which a beacon is scheduledto be received at the radio 950. T_GRANT_MIN and T_REVOKE_LEAD aredefined from requirements of the radios 940 (e.g., 802.15.4 radiorequirement). Furthermore, in some implementations, the radio 950 (e.g.,Wi-Fi transceiver) can be programmed to have timer control up to aprecision of 1 ms.

T_BEACON_ACT is the period of time a beacon is received by the radio 950(e.g., a Wi-Fi beacon) and is defined as how long a beacon signal canbe. WIFI_GRANT would not be re-asserted by timeout while the radio 950is still receiving a beacon. As an example, for a 2.4 GHz beacon sent ata 1 Mbps DSSS rate, given a typical beacon frame of approximately 300Bytes, T_BEACON_ACT is defined to be approximately 300*8*1 us, or 2.4ms.

T_BEACON_INT is defined as an interval of time for the beacon. In someimplementations, T_BEACON_INT is defined as T_GRANT_MIN+T_REVOKE_LEAD.In some implementations, the beacon interval T_BEACON_INT is defined bythe Access Point to which the radio 950 is connected. As an example, thedefault beacon interval of an Access Point is 100 TUs (or 102.4 ms).

FIG. 15J illustrates an example of a signal timing diagram with beaconskipping. When RADIO_REQ is asserted without RADIO_PRI at a time that istoo close to receiving the next scheduled beacon, WIFI_GRANT is assertedonly after the scheduled beacon has been received and completed. In thiscase, T_REQ_LATENCY (i.e., time between asserting RADIO_REQ andWIFI_GRANT being asserted consequently) may be defined as(T_GRANT_MIN+T_REVOKE_LEAD+T_BEACON_ACT).

FIGS. 15K and 15L illustrate a signal timing diagram and timing chartfor an “alarming” mode of operation for a coexistence scheme, inaccordance with some implementations.

As shown in FIG. 15K, RADIO_PRI is kept activated while in alarmingmode, and is de-activated at the termination of the last transmissionrequest (e.g., RADIO_REQ). The alarming mode may include situations inwhich critical data is being transmitted and received by the radio 940(e.g., pings from hazard detection devices being received andtransmitted to other devices). In these situations, the coexistence mustbe configured to support the receipt and transmission of this data,while synchronously transmitting data through the radio 950 (e.g.,transmitting data packets of a recorded video stream through Wi-Fi)during intervals of time when the radio 940 is not requestingtransmission access (e.g., between transmissions of the radio 940).

As shown, during an alarming mode, RADIO_PRI is first asserted, andRADIO_REQ is asserted at a time T_PRI_SETUP afterwards. Once RADIO_REQhas been asserted, the radio 950 grants transmission access by assertingWIFI_GRANT at a time T_REQ_LATENCY_A afterwards. When the RADIO_REQtransmission request from the radio 940 finishes, WIFI_GRANT is revokedat time T_REVOKE_LATENCY_A afterwards. The interval T_REQ_INTERVAL_A isan interval of time between transmission requests from the radio 940(e.g., RADIO_REQ). During this time, WIFI_GRANT is revoked, andtherefore transmission access is set aside for the radio 950 (e.g., datapackets for a video stream over Wi-Fi).

In some implementations, during an alarming mode, after assertingRADIO_REQ, the radio 940 begins transmission at a time T_REQ_LATENCY_Aafterwards regardless of whether the WIFI_GRANT is asserted.

FIG. 16 shows an illustrative co-existence circuit 1700 for managingoperations of three communications circuits, in accordance with someimplementations. In the example shown, circuitry 1700 includes 6LOWPANcircuitry 1710 (e.g., a first radio 940, FIG. 9), BLE circuitry 1720(e.g., a second radio 940), Wi-Fi circuitry 1730 (e.g., a first radio950), and OR gates 1740 and 1742. Request for Access (RFA) line 1711 maybe connected to BLE circuitry 1720 and an input of OR gate 1740. An RFAline may be asserted by a communication circuit when it requires accessto an RF medium. An RF medium can include an antenna and/or acommunications frequency. RFA line 1721 may be connected to 6LOWPANcircuitry 1710 and an input of OR gate 1740. The output of OR gate 1740may be connected to Wi-Fi circuitry 1730. Priority Line 1712 may beconnected to an input of OR gate 1742, and priority line 1722 may beconnected to an input of OR gate 1742. A priority line may be assertedby a communication circuit that is requesting high priority access tothe RF medium. The output of OR gate 1742 may be connected to Wi-Ficircuitry 1730. Grant line 1731 may be connected to 6LOWPAN circuitry1710 and BLE circuitry 1720. Grant signals may be provided on grant line1731 to indicate which communications circuit is granted access to theRF medium. Grant signals may be provided by a master circuit, which isillustrated as Wi-Fi circuitry 1730. Each of circuitries 1710, 1720, and1730 may require access to the same RF medium when communicating data.

Although the examples provided in FIGS. 16-21 are described with respectto a multi-transceiver device that includes circuitry for 6LOWPAN, BLE,and Wi-Fi transmission protocols specifically, in other implementations,the circuitry 1700 may include any combination of three or more radios940 and/or radios 950. In such implementations, the methods described inFIGS. 16-21 with respect to priority lines and how respective circuitryoperates will apply analogously. In other words, the coexistence schemesand methods described in FIGS. 16-21 are generally applicable to anymulti-radio device (e.g., smart devices having three or more radios).

The RFA lines 1711 and 1721 may be shared among both 6LOWPAN circuitry1710 and BLE circuitry 1720 so that the circuits are aware of when eachmakes a request for access. Such information sharing can assist inavoiding collision events. The RFA may be provided to Wi-Fi circuitry1730, which decides whether to grant access. The priority lines mayspecify that a particular circuit is given priority over the othercircuit and that its request to access the RF medium is of high priorityand the other communication circuits should yield where possible. Forexample, 6LoWPAN circuitry 1710 may have priority over BLE circuitry1720 during an alarm event. In the event of potential collisions for RFmedium access, master or host circuitry can control which circuitry isgranted access. The master or host circuitry can be a processor otherthan one of the communications circuits (e.g., system processor 402) orit can be implemented by an onboard processor of one of thecommunication circuits (e.g., Wi-Fi circuitry 1730).

Priority may be conveyed using one of two different approaches. Oneapproach uses direct notification. In this approach, the host (e.g.,Wi-Fi 1730) can issue grant command to the communications circuits toinform them which has priority. The grant command may not necessarily bea single Boolean value, but can include an enumeration or bit fieldindicating which circuit has priority or is allowed to assert itspriority line. In another approach, implicit notification may be used.In implicit notification, a circuit may impliedly have priority if itspriority input pin is not asserted. If its priority input pin isasserted, then it may not have priority.

The 6LoWPAN communication circuitry priority cases are shown anddescribed in Table 1.

TABLE 1 No Priority, Yield 6LO_Priority not asserted, yield to BLE toBLE Circuitry when Grant asserted but BLE_RFA also asserted Priority6LO_Priority asserted, do not yield BLE_RFA asserted No Priority, Retain6LO_Priority not asserted, do not yield to access against BLE BLE whenGrant asserted but BLE_RFA also Circuitry asserted

The BLE communications circuitry priority cases are shown and describedin Table 2.

TABLE 2 No Priority BLE_Priority not asserted, yield to 6LoWPAN whenGrant asserted but 6LO_RFA also asserted Priority BLE_Priority asserted,do not yield to 6LO_RFA asserted

The priority cases for Wi-Fi circuitry 1730 are described in connectionwith FIGS. 17A-17B. FIG. 17A shows an illustrative base case in whichboth priority lines for 6LOWPAN circuitry 1710 and BLE circuitry 1720are LOW, indicating that the these circuits are not requesting priority.In addition, there are no pulses in 6LO_RFA nor BLE_RFA, indicating that6LoWPAN 1710 and BLE circuitry 1720 are not requesting access. From timet0 to t1, the Grant line is HIGH, implying that Wi-Fi circuitry 1730 isgranting access to the RF medium. From time, t1 to time, t2, Grant isLOW and WiFi Tx is HIGH. Thus, Wi-Fi circuitry 1730 denies grant when itwishes to transmit. This is also shown between time, t3 and t4.Moreover, during the base case, 6LoWPAN circuitry 1710 and BLE circuitry1720 may be permitted to access the RF medium when Grant is HIGH.

FIG. 17B shows an illustrative case showing grant and denial of 6LoWPANcircuitry 1710 access to the RF medium based status of Grant, inaccordance with some implementations. As shown, between times t1 and t2,6LO_RFA is HIGH while Grant is HIGH, thereby enabling 6Lo Tx to go HIGH.Starting at time, t3, 6Lo Tx is initially HIGH, but this transmission isdenied at time, t4, when Grant is set LOW and WiFi Tx goes HIGH. Then,at time t5, Grant returns to HIGH, thereby enabling 6LoWPAN circuitry tocontinue transmitting.

FIGS. 18A-D shows different illustrative 6LoWPAN priority use case, inaccordance with some implementations. In particular, FIG. 18A shows anillustrative base case and FIGS. 18B-18D show priority, no priority, andRetain access against BLE priority use cases, respectively, of Table 1.As shown in the base case of FIG. 18A, 6LoWPAN circuitry 1710 requestsaccess twice and is granted access both times. In addition, there are nocollisions and 6LO_Priority and Grant are HIGH throughout.

FIG. 18B shows an illustrative priority use case for 6LoWPAN in which6LO_Priority is HIGH throughout. From times t1-t2, there are not requestfor access by either 6LO or BLE, thereby enabling Wi-Fi to revoke itsGrant and transmit. At time t3, 6LO_RFA goes HIGH and 6LO Tx transmitsfrom time t3 to t4. At time t5, Wi-Fi Tx goes HIGH. However, at time t6,6LO_RFA goes HIGH, and because 6LO has priority, Wi-FI Tx goes LOW and6LO is permitted to transmit.

Referring now to FIG. 18C, 6LO_Priority and Grant are HIGH throughout.At times t1-t2, BLE_RFA is HIGH, and because 6LO_RFA is LOW, there is noconflict, and BLE Tx is permitted to go HIGH. At times t3-t4, 6LO_RFA isHIGH, and is granted access, resulting in 6LO Tx going HIGH. Starting attime t5, BLE_RFA is HIGH, and BLE Tx begins to transmit until time, t6,at which point 6LO_RFA goes HIGH. Now, at time t6, there is a conflictbetween 6LO_RFA and BLE_RFA, but because 6LO_Priority is HIGH, 6LO Txgoes HIGH, indicating that 6LoWPAN circuitry 1710 decides to transmitdespite the assertion by BLE circuitry 1720.

Referring now to FIG. 18D, both 6LO_Priority and BLE_Priority are LOWbut circuitry 1700 is configured to permit grant 6LoWPAN circuitry 1710access in case of a collision. Starting at time t1, 6LO_RFA goes HIGHand at time t2, BLE_RFA goes HIGH, but Grant goes LOW to allow Wi-Ficircuitry to transmit until time t3. At time t3, Grant goes HIGH, atwhich time, 6LO Tx begins transmitting (as shown). BLE Tx does nottransmit because BLE circuitry 1720 does not have priority and knowsthat 6LO_RFA has already been asserted. BLE Tx may go HIGH as it detectsthe falling edge of 6LO Tx at time t4.

The priority use cases for BLE circuitry 1720 are similar to thepriority use cases of 6LoWPAN circuitry 1710. For example, if FIGS.18A-18C were used to illustrate the priority use cases of BLE circuitry1720, the 6LO priority, RFA, and Tx labels can be transposed with theBLE priority, RFA, and Tx labels.

FIGS. 19A and 19B show illustrative timing diagrams where Wi-Ficircuitry 1730 is OFF, in accordance with some implementations. WhenWi-Fi circuitry 1730 is OFF, 6LoWPAN circuitry 1710 and BLE circuitry1720 are operative to arbitrate among themselves to determine who hasaccess to the RF medium. 6LoWPAN circuitry 1710 and BLE circuitry 1720may arbitrate among themselves based on their priority line assertionsand the state of the other circuit's RFA signal. FIG. 19A illustratestiming diagrams where Wi-Fi is OFF and 6LoWPAN circuitry has priority,in accordance with some implementations. As shown, 6LO_Priority andGrant are HIGH. At time t1, 6LO_RFA goes HIGH and then goes LOW at timet2. 6LO Tx is HIGH from times t1 to t2. At time t3, 6LO_RFA goes HIGH,during which time, 6LO Tx is also HIGH. BLE_RFA goes HIGH at time t4 andremains HIGH. BLE Tx continues to yield to 6LO Tx until time t5, atwhich point 6LO_RFA goes LOW. 6LO Tx may not yield between times t4 andt5, despite the pulse on BLE_RFA, because 6LoWPAN circuitry 1710 haspriority.

FIG. 19B illustrates timing diagrams where Wi-Fi is OFF and BLEcircuitry has priority, in accordance with some implementations. Asshown, Grant and BLE_Priority are HIGH. At times t1 to t2, 6LO Tx ispermitted access to transmit since there is no collision. At time t3,6LO_RFA goes HIGH, and 6LO Tx begins transmitting. At time t4, however,BLE_RFA goes HIGH. Since BLE circuitry has priority, BLE Tx takespriority over 6LO Tx. As a result, BLE Tx goes HIGH and 6LO Tx goes LOW.

Referring now to FIG. 20, an illustrative timing diagram showing how theBLE circuitry attempts to communicate with a personal device during theidle portion of a wake packet being transmitted by 6LoWPAN circuitryduring a NCCA period, in accordance with some implementations. Duringthe NCCA period, Wi-Fi circuitry 1730 is not yet turned ON, therefore6LoWPAN circuitry 1710 and BLE circuitry 1720 may arbitrate amongstthemselves to determine who has access to the RF medium. For purposes ofthis timing diagram, assume that the 6LoWPAN has priority (e.g., becausehazard detection system has raised its alarm). FIG. 20 shows that theNCCA wake packet transmission cycle has a period including an activeportion (as evidenced by the HIGH pulse) and an idle portion (asevidenced by the LOW signal). The 6LoWPAN_RFA may track the activeportion of each wake packet. Since 6LoWPAN circuitry 1710 has priority,it controls access to the RF medium regardless of any RFA by BLEcircuitry 620. This is shown in the FIG., as evidenced by 6LoWPAN Txgoing HIGH in concert with the 6LoWPAN pulses. BLE_RFA is shown toremain HIGH throughout the timing diagram, thus indicating BLE circuitry1720's desire to attempt communications with a personal device (notshown). BLE circuitry 1720 is permitted to communicate during the idleportion of each wake packet transmission. This is shown where BLE Txgoes HIGH when 6LoWPAN Tx goes LOW, and vice versa.

During the BLE Tx HIGH signal period, BLE circuitry 1720 attempts tocommunicate with one or more personal devices. BLE circuitry 1720 may dothis by 1) advertising its presence to the personal device (e.g., onchannel 37 of a BLE protocol), 2) authenticating the personal device(e.g., on channel 38 of the BLE protocol), and 3) commencing datatransfer with the personal device (e.g., on channel 39 of the BLEprotocol). BLE circuitry 1720 may perform all three steps during asingle BLE Tx session or over a series of BLE Tx sessions. The datatransfer can specify instructions for altering the state of the system.For example, if the system is alarming, the instruction can contain ahush instruction that commands the system to change from an alarmingstate to a hush state.

FIG. 21 shows illustrative timing diagrams of exemplary BLE advertise,connect, and data transfer activity during BLE transmissions, inaccordance with some implementations. The BLE operations of advertise,connect, and data transfer may occur during BLE_Tx activity, which occurwhen BLE_Tx is HIGH. As shown in FIG. 21, the BLE operations areperformed in one of the four BLE_Tx activity windows. BLE Advertise mayoccur during BLE_Tx activity window 1, and BLE connect may occur duringBLE_Tx activity window 2. After a connection is made, BLE data may betransmitted between a personal device and the system during windows 3and 4.

FIG. 22 is a flow diagram illustrating a method of coexistence usingbypass circuitry, in accordance with some implementations. In someimplementations, the method 2200 is performed at an electronic device(e.g., devices of a smart home environment 100, FIGS. 1 and 12; smartdevices 204 and/or hub device 180 of smart home network 202, FIG. 2)having a plurality of transceivers and antennas (e.g., smart device 204,FIG. 14, having one or more radios 940 and/or radios 950, and antennas1402). More specifically, in some implementations, the method 2200 isperformed by one or more components of the electronic device (e.g.,communications module 942 of smart device 204, or a front end module1400 of the communications module). For ease of reference, the methodsherein will be described as being performed by an electronic device(e.g., smart device 204). FIG. 22 corresponds to instructions stored ina computer memory or other computer-readable storage medium (e.g.,memory 606 of the hub device 180), or instructions stored in the memoryof one or more components of the electronic device (e.g., memory of thecommunications module 942, not illustrated).

The electronic device (e.g., smart device 204, which is a camera)includes a plurality of transceivers (e.g., radio(s) 940 and radio(s)950, FIG. 14), one or more processors, and memory storing instructionsfor execution by the one or more processors. The electronic devicedetects (2204) whether a second transceiver (e.g., radio 950) of theplurality of transceivers is not transmitting signals via a secondantenna (e.g., antenna 1402-2) coupled to the second transceiver. Insome implementations, a bypass signal is produced (2202) when the secondtransceiver is active, where detecting (2204) whether the secondtransceiver is transmitting signals includes (2206) detect the bypasssignal. For example, a bypass signal is produced and detected onconnection 1410 (FIG. 14) when radio 950 is transmitting.

In accordance with detecting that the second transceiver is nottransmitting signals via the second antenna, a first transceiver (e.g.,radio 940) of the plurality of transceivers is coupled (2208) to a firstantenna via an amplifier such that a signal received by the firstantenna is amplified by the amplifier prior to being passed to the firsttransceiver. In some implementations, the amplifier is a low-noiseamplifier (e.g., low noise amplifier 1406-2, FIG. 14).

In accordance with detecting that the second transceiver is transmittingsignals via the second antenna, the first transceiver is coupled (2210)to the first antenna via a bypass line (e.g., bypass line 1408) suchthat a signal received by the first antenna is not amplified by theamplifier prior to being passed to the first transceiver.

In some implementations, the first and second antennas receive andtransmit signals at the same frequency (e.g., 2.4 GHz).

FIGS. 23A-23F are flow diagrams illustrating methods of using controlsignals in a coexistence scheme, in accordance with someimplementations. In some implementations, the methods 2300 and 2330 areperformed at an electronic device having a plurality of transceivers andantennas (e.g., smart device 204 of FIGS. 9 and 15A-15B, having one ormore radios 940 and/or radios 950). More specifically, in someimplementations, the methods 2300 and 2330 are performed by one or morecomponents of the camera device (e.g., communications module 942 ofsmart device 204). For ease of reference, the methods herein will bedescribed as being performed at a camera device (e.g., smart device 204of FIG. 15A, a camera). FIGS. 23A-23F correspond to instructions storedin a computer memory or other computer-readable storage medium (e.g.,memory 606 of the hub device 180), or instructions stored in the memoryof one or more components of the electronic device (e.g., memory of thecommunications module 942, not illustrated).

The camera device includes a plurality of distinct transceiversconfigured for communication over respective communication protocols(e.g., radio 940 and radios 950, which includes radios 950-1 and 950-2,FIGS. 15A-15B), one or more processors, and memory storing instructionsfor execution by the one or more processors.

In performing the method 2300, the camera device communicates (2302)using a first transceiver of the plurality of distinct transceivers, thefirst transceiver configured to transmit and receive, over a first oneof the communication protocols, signals for configuring the cameradevice (e.g., radio 950-1 of radios 950, FIGS. 15A-15B). In someimplementations, the first communication protocol is (2304) based on theBluetooth Low Energy standard. In some implementations, communicating(2302) using the first transceiver includes transmitting (2306) datacomprising a video format configured for low-bandwidth transmissions(e.g., a low resolution encoded video stream).

The camera device communicates (2308) with one or more smart homedevices using a second transceiver of the plurality of transceivers. Thesecond transceiver (e.g., radio 940, FIG. 15A) is configured to transmitand receive, over a second one of the communication protocols, signalscomprising one or more of alerts, control signals and status informationto and from the one or more smart home devices (e.g., emergency alertsfrom hazard detectors 104, FIG. 1). In some implementations, the secondcommunication protocol is based (2310) on the IEEE 802.15.4 standard. Insome implementations, communicating (2308) using the second transceiverincludes (2312) transmitting data comprising the video format configuredfor low-bandwidth transmissions (e.g., a low resolution encoded videostream). In some implementations, communicating (2308) using the secondtransceiver includes (2314) receiving intermittent signals from the oneor more smart home devices and/or retransmitting received signals fromthe one or more smart home devices, concurrently with the transmissionof data using a third transceiver (e.g., receiving emergency pings fromconnected smart hazard detectors 104 using radio 940 (FIG. 15A) whiletransmitting video data over Wi-Fi radio 950-2 (FIGS. 15A-15B)). In someimplementations, the transmission of data using the third transceiver istemporarily suspended (2316) while receiving signals from the one ormore smart home devices and/or retransmitting received signals from theone or more smart home devices. For example, radio 940 and radios 950coordinate transmission access such that the radio 940 and radios 950are not both simultaneously transmitting signals at a given time (e.g.,communications module 942 moderates transmission access by the radio 940and radios 950, and selectively grants/denies transmission access to theradio 940 and radios 950).

Referring now to FIG. 23B, the camera device communicates (2318) usingthe third transceiver of the plurality of transceivers. The thirdtransceiver (e.g., radio 950-2 of radios 950, FIGS. 15A-15B) isconfigured to transmit and receive, over a third one of thecommunication protocols, data corresponding to video captured by thecamera device. In some implementations, the third communication protocolis based (2320) on the IEEE 802.11 standard. In some implementations,the data comprises (2322) a video format configured for high-bandwidthtransmissions (e.g., high resolution video streaming of videosurveillance footage using Wi-Fi). In some implementations,communicating (2318) using the third transceiver includes (2324)receiving and transmitting data at a data rate that is higher than adata rate at which the camera device communicates using the firsttransceiver and/or a data rate at which the camera device communicatesusing the second transceiver (e.g., streaming high-resolution videousing Wi-Fi radio 950-2, while streaming low-resolution video using802.15.4 radio 940, FIGS. 15A-15B).

In some implementations, the camera device receives (2326) signals fromthe one or more smart home devices over the second communicationprotocol, and retransmits (2328) the signals to one or more other smarthome devices (e.g., receiving and retransmitting emergency pings fromconnected smart hazard detectors 104 using radio 940, FIG. 15A).

Referring now to FIG. 23C, the camera device may perform the method 2330additionally to and/or in conjunction with the method 2300. Inperforming the method 2330, in some implementations, the camera devicegrant or deny transmission access to the first transceiver (e.g., radio950-1 of radios 950, FIGS. 15A-15B, such as Bluetooth LE), the secondtransceiver (e.g., radio 940, FIG. 15A, such as 802.15.4), and/or thethird transceiver (e.g., radio 950-2 of radios 950, FIGS. 15A-15B, suchas Wi-Fi) of the plurality of distinct transceivers of the cameradevice, where the transceivers are configured for communication overrespective communication protocols.

In some implementations, granting or denying transmission access (2332)includes (2334) detecting activation of a priority control signal (e.g.,assertion of RADIO_PRI signal on control line 1500-1, FIG. 15A). In someimplementations, the activated priority control signal corresponds(2336) to an alarming mode of the second transceiver (e.g., incomingemergency alerts from a hazard detector 104). In response to detectingactivation of the priority control signal, transmission access isgranted (e.g., by the “master” transceiver, such as radio(s) 950, FIG.15A) to the second transceiver (e.g., e.g., 802.15.4 radio 940) andtransmission access is denied to the third transceiver (e.g., Wi-Firadio 950-2).

In some implementations, an activated priority control signal isdetected (2304) (e.g., an already asserted RADIO_PRI signal on controlline 1500-1 is detected). While detecting the activated priority controlsignal (2342), activation of a radio request control signal by thesecond transceiver is detected (2344) (e.g., assertion of RADIO_REQsignal on control line 1500-2). In response to detecting activation ofthe radio request control signal by the second transceiver, transmissionaccess is granted (2346) to the second transceiver and transmissionaccess is denied to the third transceiver. In some implementations,granting transmission access to the second transceiver and denyingtransmission access to the third transceiver includes (2348) activatingthe grant control signal (e.g., asserting WIFI_GRANT signal on controlline 1500-3, FIG. 15A). A corresponding example of steps 2340 through2348 is illustrated in FIG. 15K.

In some implementations, while detecting the activated priority controlsignal, a transmission request is detected (2350) by the thirdtransceiver. In some implementations, the transmission request by thethird transceiver is detected (2352) while transmission access isgranted to the second transceiver. In response to detecting thetransmission request by the third transceiver, and while detecting theactivated radio request control signal by the second transceiver,transmission access continues (2354) to be granted to the secondtransceiver while transmission access continues to be denied to thethird transceiver. Thus, in some implementations, while the prioritycontrol signal is activated, the third transceiver is not permitted totransmit data.

In some implementations, while continuing to detect the activated radiorequest control signal and the activated priority control signal,transmission access continues (2356) to be granted to the secondtransceiver and transmission access continues to be denied to the thirdtransceiver.

Referring now to FIG. 23D, in some implementations, while detecting theactivated priority control signal, deactivation of the radio requestcontrol by the second transceiver is detected (2360) (e.g., de-assertionof RADIO_REQ signal on control line 1500-2). In response to detectingdeactivation of the radio request control signal by the secondtransceiver, transmission access to the second transceiver is revoked(2362) and transmission access to the third transceiver is granted. Insome implementations, revoking transmission access to the secondtransceiver and granting transmission access to the third transceiverincludes (2364) deactivating the grant control signal (e.g.,de-asserting WIFI_GRANT signal on control line 1500-3). A correspondingexample of steps 2360 through 2364 is illustrated in FIG. 15K.

In some implementations, a deactivated priority control signal isdetected (2366) (e.g., an already de-asserted RADIO_PRI signal oncontrol line 1500-1 is detected). While detecting the deactivatedpriority control signal (2368), activation of the radio request controlsignal by the second transceiver is detected (2370). In response todetecting activation of the radio request control signal by the secondtransceiver, transmission access is granted (2372) to the secondtransceiver and transmission access is denied to the third transceiver.In some implementations, while transmission access is granted to thesecond transceiver, a transmission request by the third transceiver isdetected (2374). In some implementations, the transmission request bythe third transceiver is detected (2376) while detecting the activatedradio request control signal. In some implementations, the transmissionrequest by the third transceiver is (2378) a high priority transmissionrequest (e.g., a transmission request within an access category above BE(Best Effort), VI (Video), and/or VO (Voice)). In response to detectingthe transmission request by the third transceiver, transmission accessis revoked (2380) to the second transceiver and transmission access isgranted to the third transceiver. In some implementations, whiletransmission access is granted to the third transceiver, a high prioritytransmission by the third transceiver is detected (2382) to be inprogress. Upon completion of the high priority transmission,transmission access is granted (2384) to the second transceiver andtransmission access is revoked to the third transceiver. A correspondingexample of steps 2366 through 2384 is illustrated in FIG. 16F.

In some implementations, the camera device communicates (2302) using thefirst transceiver, communicates (2308) with one or more smart homedevices using the second transceiver, and communicates (2318) using thethird transceiver (where the steps 2302, 2308, and 2318 may be performedin accordance with any of the implementations described with respect toFIGS. 23A-23B).

FIGS. 24A-24D illustrate various types of antennas for use with thevarious devices disclosed herein. For example, the antenna typesillustrated in FIGS. 24A-24D are optionally used with the camera devicesillustrated in FIGS. 25-29, discussed below. In accordance with someimplementations, each of the antenna types is optionally used withvarious communication protocols, such as ZigBee, Z-Wave, Insteon,EuOcean, Thread, OSIAN, Bluetooth Low Energy and the like. In accordancewith some implementations, each of the antenna types is optionally usedwith various wired or wireless protocols, such as Ethernet, UniversalSerial Bus (USB), FIREWIRE, Long Term Evolution (LTE), Global System forMobile Communications (GSM), Enhanced Data GSM Environment (EDGE), codedivision multiple access (CDMA), time division multiple access (TDMA),Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or anyother suitable communication protocol.

FIG. 24A illustrates an example of an external antenna, external antenna2402, for use with the various devices disclosed herein. An externalantenna is sometimes also called a whip antenna. In someimplementations, the external antenna 2402 is coupled to a device, suchas a camera device, via a coaxial connector. In some implementations,the external antenna 2402 is coupled to the device via any suitablecable connector, such as BNC, F-type, FME, MC-Card, MCX, MMCX, QMA, SMB,SSMB, and the like. In some implementations, the external antenna ismounted to the device casing. In some implementations, the externalantenna is a dipole antenna (e.g., with a size of ½ wavelength). In someimplementations, the external antenna is a monopole antennal (e.g., witha size of ¼ wavelength). In some instances, the optimal orientation of adipole or monopole type external antenna is perpendicular to the localground plane of the device. In some implementations, the externalantenna includes a hinge or swivel to enable a user to adjust the angleand positioning of the antenna relative to the device.

In some implementations, the external antenna 2402 comprises a verticalwire and/or one or more traces on a circuit board, typically encased ina plastic housing. In some implementations, the external antenna isexternal to the main housing of the device and is perpendicular to thelargest dimension(s) of the device. External antennas may achieve highefficiency and have, in general, better immunity to the self-generatednoise of the device than internal/embedded antenna. While externalantennas may provide superior performance, there are disadvantages insome instances due to: susceptibility to damage, additionalmanufacturing cost, and potential performance degradation due to theuser's interaction with the exposed antenna.

FIGS. 24B-24D illustrate various types of internal antennas for use withthe various devices disclosed herein. Internal antennas are sometimescalled embedded antennas. As used herein, an internal antenna includesany antenna that lies completely within the device casing. Internalantennas are generally not implemented within metal casings as the metalcasing will degrade efficiency. The internal antennas are coupled to acommunications module. The communications module is sometimes called aradio module or a radio. In some implementations, the communicationsmodule comprises a communications chip. In some implementations, aninternal antenna is coupled to a communications module via one or morecontrolled impedance structures, such as coaxial cable, controlledimpedance circuit board traces (e.g., microstrip or stripline),spring-loaded pogo pins or spring fingers, flex circuits with controlledimpedance lines, and the like. In some implementations, the internalantenna is coupled to the communications module via one or more filters,amplifiers, and/or switches. Cables and traces will introduce losses andshould be carefully considered. For example, cables and traces createopportunities for noise to enter the receiver system.

Internal antennas are susceptible to interference with other devicecomponents (including other internal antennas). In some instances, theprimary noise source is the digital circuitry, such as the processor(s)and memory. For example, in some instances, processor clocks, high-speedmemory, displays, and graphics processors are the highest sources ofnoise and produce the widest range of frequencies. In someimplementations, the digital electronics are shielded with board-mountedshield cans. In some implementations, the antenna(s) are positioned asfar from the largest noise sources as possible. In some implementations,the antenna interconnect(s) are routed away from the largest noisesources. In some implementations, non-shielded antenna interconnects(e.g., spring fingers or pogo pins) are position to limit exposure tothe largest noise sources.

FIG. 24B illustrates an example of a sheet metal antenna for use withthe various devices disclosed herein. A sheet metal antenna is alsosometimes called a stamped metal antenna. In FIG. 24B, sheet metalantenna 2404 is mounted on circuit board 2406 and coupled tocommunications module 2408. In some implementations, sheet metal antenna2404 is mounted perpendicular to the plane of circuit board 2406. Insome implementations, sheet metal antenna 2404 is mounted parallel tothe plane of circuit board 2406. In some implementations, sheet metalantenna 2404 is an inverted-F style antenna. In some implementations,sheet metal antenna 2404 comprises a patch antenna. In someimplementations, the patch antenna is a printed patch antenna. In someimplementations, the patch antenna is printed on a surface of amulti-layer circuit board. In some implementations, the patch antennacomprises a directional antenna with a primary lobe of radiationoriented away from the ground plane of the device.

The size and shape of the local ground plane and the relatively closespacing of the ground plane to the antenna element have an impact on theantenna design. Sheet metal antennas are optimally placed on the edge ofa ground plane, such as the edge of a circuit board, or on top of aplanar ground plane surface. Thus, a sheet metal antenna is optimallynot surrounded by ground planes and/or other conducting surfaces.

FIG. 24C illustrates an example of a board antenna for use with thevarious devices disclosed herein. A board antenna is sometimes alsocalled a printed circuit board (PCB) antenna or a PCB trace antenna. InFIG. 24C, board antenna 2412 is mounted on circuit board 2410 and iscoupled to communications module 2414. Board antennas are generallyaffected by the circuit board's substrate properties, such as thedielectric constant and dissipation factor. In some implementations, theboard antenna 2412 comprises a single-ended antenna. In someimplementations, the board antenna 2412 comprises a differentialantenna. In some implementations, the board antenna 2412 comprises aYagi antenna. In some implementations, the board antenna 2412 comprisesan F antenna. In some implementations, the board antenna 2412 comprisesan inverted-F antenna. In some implementations, the board antenna 2412is laminated on the circuit board 2410 surface. In some implementations,the board antenna 2412 occupies one or more layers on the circuit board2410.

FIG. 24D illustrates an example of a chip antenna for use with thevarious devices disclosed herein. In FIG. 24D, antenna chip 2422 ismounted on board 2420. In some implementations, chip antennas are placedon a circuit board like a standard circuit component, although theseantennas generally suffer in efficiency. Chip antennas are generallyaffected by the circuit board's substrate properties, such as thedielectric constant and dissipation factor. The circuit board'ssubstrate material reduces the resonant length of the antenna, whichresults in a reduction of the usable bandwidth. The circuit boardsubstrate also introduces a loss mechanism and reduces the antenna'sefficiency. In some instances where the available board space for theantenna is limited, a chip antenna is an optimal antenna type. In someimplementations, the chip antenna 2422 comprises a ceramic chip antenna.In some implementations, the chip antenna 2422 comprises an F antenna.In some implementations, the chip antenna 2422 comprises an inverted-Fantenna. In some implementations, the chip antenna 2422 comprises amonopole antenna.

As previously discussed, FIG. 11D illustrates an example of adhesiveantennas for use with the various devices disclosed herein. Adhesiveantennas 1104-1 and 1104-2 are mounted to cover 1102 (also sometimescalled a casing or a housing). In some implementations, the adhesiveantenna 1104 comprises a tape antenna. In some implementations, theadhesive antenna 1104 comprises a sticker antenna. In someimplementations, the adhesive antenna 1104 comprises a conductive paintantenna. In some implementations, the adhesive antenna 1104 comprises awire antenna.

FIGS. 25A-25F illustrate various assembly views of a camera device, inaccordance with some implementations. FIG. 25A shows an exterior view ofcamera device 2500 including casing 2501, lens 2516, status LED 2514,microphone 2508, status LED 2512, light sensor 2510, LED 2502, motionsensor 2504, and speaker 2506. In some implementations, casing 2501comprises a plastic casing. In some implementations, LED 2502 is aninfrared (IR) LED. In some implementations, status LED 2512 indicateswhether camera device 2500 is coupled to another device (such as arouter) via a wireless connection. In some implementations, status LED2512 indicates the WPS status of camera device 2500. In someimplementations, status LED 2514 indicates the camera status of cameradevice 2500. In some implementations, motion sensor 2504 is a passiveinfrared sensor for motion detection. In some implementations, lightsensor 2510 comprises an IR-cut removable sensor. In someimplementations, camera device 2500 switches between color mode andinfrared mode based on output from light sensor 2510. In someimplementations, LED 2502 is utilized to provide illumination whencamera device 2500 is in infrared mode.

FIG. 25B shows another exterior view of camera device 2500 includingcasing 2501, lens 2516, status LED 2514, microphone 2508, status LED2512, light sensor 2510, LED 2502, motion sensor 2504, speaker 2506, andheight adjustor 2520. In some implementations, height adjustor 2520comprises an adjustment ring for adjusting the positioning of cameradevice 2500. In some implementations, camera device 2500 includes astorage card slot, such as a Micro SD card slot (not shown).

FIG. 25C shows another exterior view of camera device 2500 includingcasing 2501, power connector 2528, I/O connector 2526, connectivity port2530, height adjustor 2520, wireless affordance 2522, and reset 2524. Insome implementations, I/O connector 2526 comprises a DI/DO connector. Insome implementations, connectivity port 2530 comprises an RJ45connection port. In some implementations, reset 2524 is utilized toreset the state of camera device 2500. In some implementations, wireaffordance 2522 comprises a WPS button for establishing a wirelessconnection.

FIG. 25C also shows regions 2527 and 2529 on casing 2501. In someimplementations, camera device 2500 includes one or more externalantenna, such as antenna 2402 in FIG. 24A. In some implementations, anexternal antenna is located in region 2527. In some implementations, anexternal antenna is located in region 2529. In some implementations, anexternal antenna is located at another position on camera device 2500.In some implementations, the external antenna is utilized with one ormore of a variety of custom or standard wireless protocols (e.g., IEEE802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart,ISA100.11a, WirelessHART, MiWi, etc.).

FIG. 25D shows an interior view of camera device 2500 including casing2501, circuit board 2541, microphone 2508, speaker 2506, and lens 2516.Circuit board 2541 includes memory 2542, antenna 2540, LED 2502, andmotion sensor 2504. In some implementations, memory 2542 comprises flashmemory. In some implementations, antenna 2540 comprises a sheet metalantenna (e.g., antenna 2404 in FIG. 24B). In some implementations,antenna 2540 is utilized with Wi-Fi and/or Bluetooth wirelesscommunications. In some implementations, antenna 2540 is utilized with15.4 wireless communications. In some implementations, an externalantenna (e.g., an external antenna located in region 2527 or 2529 inFIG. 25C) is utilized for 15.4 wireless communications and antenna 2540is utilized with Wi-Fi communications. In some implementations, anexternal antenna is utilized for Bluetooth communications and antenna2540 used for Wi-Fi communications.

FIG. 25D also shows regions 2550, 2552, 2556, 2558, and 2560 on casing2501 and region 2560 on circuit board 2541. In some implementations,camera device 2500 includes one or more internal antennas in addition toantenna 2540. In some implementations, the one or more internal antennasinclude a sheet metal antenna (e.g., antenna 2404 in FIG. 24B). In someimplementations, the one or more internal antennas include a boardantenna (e.g., antenna 2414 in FIG. 24C). In some implementations, theone or more internal antennas include a chip antenna (e.g., antenna 2422in FIG. 24D). In some implementations, the one or more internal antennasinclude an adhesive antenna (e.g., antenna 1104-1 in FIG. 11D).

In some implementations, an internal antenna, such as an adhesiveantenna, is located in region 2550. In some implementations, an internalantenna, such as an adhesive antenna, is located in region 2552. In someimplementations, an internal antenna, such as an adhesive antenna, islocated in region 2556. In some implementations, an internal antenna,such as an adhesive antenna, is located in region 2558. In someimplementations, an internal antenna, such as a chip antenna, is locatedin region 2554. In some implementations, an internal antenna is locatedat another position within camera device 2500. In some implementations,the internal antenna is utilized with one or more of a variety of customor standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee,6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART,MiWi, etc.). In some implementations, the internal antenna is utilizedfor 15.4 wireless communications and antenna 2540 is utilized for Wi-Ficommunications.

FIG. 25E shows a first side of circuit board 2541. The first side ofcircuit board 2541 includes memory 2542, antenna 2540, LED 2502, andmotion sensor 2504. The first side of circuit board 2541 also includesconnections to speaker 2506 and microphone 2508. FIG. 25E also showsregion 2554 and region 2560. In some implementations, an internalantenna, such as a chip antenna or a board antenna, is located in region2560.

FIG. 25F shows a second side of circuit board 2541. The second side ofcircuit board 2541 includes processor 2545, power connector 2528, I/Oconnector 2526, card slot 2543, ethernet port 2530, wireless affordance2522, reset 2524, energy storage device 2546, and wirelesscommunications module 2548. In some implementations, card slot 2543comprises a MicroSD card slot. Wireless communications module 2548 iscoupled to antenna 2540. In some implementations, wirelesscommunications module 2548 comprises a wireless communications chip. Insome implementations, wireless communications module 2548 comprisescommunications module 942. In some implementations, wirelesscommunications module 2548 is located on a separate board bonded tocircuit board 2541. In some implementations, wireless communicationsmodule 2548 is utilized with one or more of a variety of custom orstandard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee,6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART,MiWi, etc.).

FIG. 25F also shows region 2562 on circuit board 2541. In someimplementations, an internal antenna, such as a chip antenna or a boardantenna, is located in region 2562. In some implementations, cameradevice 2500 includes multiple antennas and each antenna is coupled to adistinct communications module. For example, an external antenna iscoupled to a first communications module for use with Wi-Ficommunications and antenna 2540 is coupled to a second communicationsmodule for use with Bluetooth communications. In some implementations,the camera device 2500 includes a controller module to manage operationsof the first and second communications modules. In some implementations,one or more of the arbitration methods and/or schemes described herein(e.g., as discussed above with respect to FIG. 15A) are utilized tomanage operations between communications modules, radios, and/orantennas. In some implementations, one or more of the co-existencemethods and/or circuits described herein (e.g., as discussed above withrespect to FIG. 16) are utilized to manage operations betweencommunications modules, radios, and/or antennas. In someimplementations, camera device 2500 includes multiple antennas coupledto a single communications module. In some implementations, cameradevice 2500 includes an antenna coupled to multiple communicationsmodules.

In some implementations, a communications module is located in region2560 (FIG. 25E). In some implementations, a communications module islocated in region 2554 (FIG. 25E). In some implementations, acommunications module is located in region 2562 (FIG. 25F). For example,camera device 2500 includes a first antenna (e.g., sheet metal antenna2540 in FIG. 25E) coupled to a first communications module (e.g.,wireless communications module 2548 in FIG. 25F) and a second antenna,such as adhesive antenna (e.g., located in region 2552 in FIG. 25D),coupled to a second communications module (e.g., located in region 2554in FIG. 25D). As another example, camera device 2500 includes a firstantenna (e.g., sheet metal antenna 2540 in FIG. 25E) coupled to a firstcommunications module (e.g., wireless communications module 2548 in FIG.25F) and a second antenna, such as a chip antenna (e.g., located inregion 2554 in FIG. 25D), coupled to a second communications module(e.g., located in region 2560 in FIG. 25D).

In some implementations, camera device 2500 includes a communicationscontroller for managing communications via multiple antennas and/ormultiple radios. In some implementations, the communications controllercomprises a communications module (e.g., communications module 942 inFIG. 14). In some implementations, the communications controller islocated in region 2560 (FIG. 25E). In some implementations, thecommunications controller is located in region 2554 (FIG. 25E). In someimplementations, the communications controller is located in region 2562(FIG. 25F). For example, camera device 2500 includes: (1) a firstantenna (e.g., sheet metal antenna 2540 in FIG. 25E) coupled to a firstcommunications module (e.g., wireless communications module 2548 in FIG.25F); (2) a second antenna, such as an external antenna (e.g., locatedin region 2527 in FIG. 25C), coupled to a second communications module(e.g., located in region 2560 in FIG. 25D); and (3) a communicationscontroller (e.g., located in region 2562 in FIG. 25F).

FIGS. 26A-26J illustrate various assembly views of a camera device, inaccordance with some implementations. FIG. 26A shows an exterior view ofcamera device 2600 including casing 2601, lens 2602, LEDs 2604, antenna2606, power LED 2608, reset affordance 2610, light sensor 2612,microphone 2614, and stand 2616. In some implementations, casing 2601comprises a plastic casing. In some implementations, stand 2616comprises a metal stand. In some implementations, LEDs 2602 are aninfrared (IR) LEDs. In some implementations, camera device 2600 includesa motion sensor such as a passive infrared sensor for motion detection.In some implementations, light sensor 2612 comprises an IR-cut removablesensor. In some implementations, camera device 2600 switches betweencolor mode and infrared mode based on output from light sensor 2612. Insome implementations, LEDs 2602 are utilized to provide illuminationwhen camera device 2600 is in infrared mode. In some implementations,reset affordance 2610 is utilized to reset the camera device 2600 to aknown state. In some implementations, microphone 2614 is utilized todetect noise above a predefined threshold. In some implementations,microphone 2614 is utilized to receive voice commands. In someimplementations, antenna 2606 comprises external antenna 2402. In someimplementations, antenna 2606 is utilized with one or more of a varietyof custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi,ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a,WirelessHART, MiWi, etc.). In some implementations, antenna 2606 isutilized with Wi-Fi and/or Bluetooth wireless communications. In someimplementations, antenna 2606 is utilized with 15.4 wirelesscommunications. In some implementations, an internal antenna is utilizedfor 15.4 wireless communications and antenna 2606 is utilized with Wi-Ficommunications. In some implementations, an internal antenna is utilizedfor Bluetooth communications and antenna 2606 used for Wi-Ficommunications.

FIG. 26A also shows region 2603 on casing 2601. In some implementations,camera device 2600 includes one or more additional external antennas(e.g., external antenna 2402, FIG. 24A) in addition to external antenna2606. In some implementations, an external antenna is located in region2603. For example, an external antenna similar in design to antenna 2606is located in region 2603. In some implementations, antenna 2606 isutilized for communications at a first wavelength and the one or moreadditional external antennas are utilized for communications at one ormore wavelengths distinct from the first wavelength. For example, theadditional external antenna is utilized for 15.4 wireless communicationsand antenna 2606 is utilized for Wi-Fi communications. In someimplementations, an external antenna is located at another position oncamera device 2600.

FIGS. 26B and 26C show additional exterior views of camera device 2600.FIG. 26B shows an exterior view of the front of camera device 2600including casing 2601, lens 2602, LEDs 2604, antenna 2606, power LED2608, light sensor 2612, microphone 2614, and stand 2616. FIG. 26C showsan exterior view of a side of camera device 2600 including casing 2601,LEDs 2604, antenna 2606, reset affordance 2610, and stand 2616. In someimplementations, camera device 2600 further includes a power port and/ora wired communications port, such as an Ethernet port.

FIG. 26D shows an interior view of camera device 2600 including casing2601, circuit board 2622, circuit board 2620, and lens 2602. Circuitboard 2622 includes microphone 2614 and processor 2650. In someimplementations, processor 2650 comprises a system-on-chip (SoC).Circuit board 2620 includes LEDs 2604.

FIG. 26D also shows regions 2625, 2627, 2629, 2631, 2637, and 2639 oncasing 2601, region 2623 on circuit board 2622, and regions 2633 and2635 on circuit board 2620. In some implementations, camera device 2600includes one or more internal antennas. In some implementations, the oneor more internal antennas include a sheet metal antenna (e.g., antenna2404 in FIG. 24B). In some implementations, the one or more internalantennas include a board antenna (e.g., antenna 2414 in FIG. 24C). Insome implementations, the one or more internal antennas include a chipantenna (e.g., antenna 2422 in FIG. 24D). In some implementations, theone or more internal antennas include an adhesive antenna (e.g., antenna1104-1 in FIG. 11D).

In some implementations, an internal antenna, such as an adhesiveantenna, is located in region 2625. In some implementations, an internalantenna, such as an adhesive antenna, is located in at least one ofregions 2627, 2629, 2631, 2637, and 2639. In some implementations, aninternal antenna, such as a chip antenna, is located in region 2625. Insome implementations, an internal antenna, such as a board antenna, islocated in region 2635. In some implementations, an internal antenna,such as a sheet metal antenna, is located in region 2633. In someimplementations, an internal antenna is located at another positionwithin camera device 2600. In some implementations, the internal antennais utilized with one or more of a variety of custom or standard wirelessprotocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave,Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.). In someimplementations, the internal antenna is utilized for 15.4 wirelesscommunications and antenna 2606 (FIG. 26A) is utilized for Wi-Ficommunications.

FIG. 26E shows another interior view of camera device 2600 includingcasing 2601, circuit board 2632, antenna 2606, and lens 2602. In someimplementations, lens 2602 is mounted to board 2632. In someimplementations, antenna 2606 is communicatively coupled to circuitboard 2622.

FIG. 26E also shows regions 2625, 2627, 2629, 2631, 2641, and 2643 oncasing 2601 and region 2647 on board 2632. In some implementations, aninternal antenna, such as an adhesive antenna, is located in at leastone of regions 2625, 2627, 2629, 2631, 2641, and 2643. In someimplementations, an internal antenna, such as a chip antenna, is locatedin region 2647. In some implementations, an internal antenna is locatedat another position within camera device 2600. In some implementations,the internal antenna is utilized with one or more of a variety of customor standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee,6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART,MiWi, etc.). In some implementations, the internal antenna is utilizedfor Bluetooth wireless communications and antenna 2606 (FIG. 26A) isutilized for Wi-Fi communications.

FIG. 26F shows a first side of circuit board 2622. The first side ofcircuit board 2622 includes processor 2650 and microphone 2614. FIG. 26Falso shows region 2623. In some implementations, an internal antenna,such as a chip antenna or a board antenna, is located in region 2623. Insome implementations, an internal antenna is located at another locationon circuit board 2622.

FIG. 26G shows a second side of circuit board 2622. The second side ofcircuit board 2622 includes reset affordance 2610, communications port2626, card slot 2628, and power connector 2630. In some implementations,communications port 2626 comprises an Ethernet port. In someimplementations, card slot 2628 comprises a MicroSD card slot. FIG. 26Galso shows circuit board 2624 mounted to circuit board 2622. Circuitboard 2624 includes wireless communications module 2632. In someimplementations, wireless communications module 2632 utilizes antenna2606 for wireless communication (e.g., Wi-Fi communications). FIG. 26Galso shows region 2645. In some implementations, an internal antenna,such as a sheet metal antenna or a board antenna, is located in region2645. In some implementations, an internal antenna is located at anotherlocation on circuit board 2622.

FIG. 26H shows circuit board 2620. Circuit board 2620 includes aplurality of LEDs 2604 (e.g., 30 LEDs), such as LED 2604-1. Circuitboard 2620 also includes light sensor 2612. FIG. 26H also showspartition 2652. In some implementations, partition 2652 is affixed tocircuit board 2620. In some implementations, partition 2652 preventslight from LEDs 2604 from directly entering lens 2602. In someimplementations, an internal antenna is located on circuit board 2620.

FIG. 26I shows a first side of circuit board 2634 and lens 2602. In someimplementations, lens 2602 is mounted on circuit board 2634. FIG. 26Ialso shows region 2647. In some implementations, an internal antenna,such as a chip antenna or a board antenna, is located in region 2647. Insome implementations, an internal antenna is located at another locationon circuit board 2634.

FIG. 26J shows a second side of circuit board 2634. FIG. 26J also showsregion 2649. In some implementations, an internal antenna, such as achip antenna or a sheet metal antenna, is located in region 2649. Insome implementations, an internal antenna is located at another locationon circuit board 2634.

In some implementations, camera device 2600 includes multiple antennasand each antenna is coupled to a distinct communications module. Forexample, antenna 2606 is coupled to a first communications module foruse with Wi-Fi communications and an internal antenna is coupled to asecond communications module for use with Bluetooth communications. Insome implementations, the camera device 2600 includes a controllermodule to manage operations of the first and second communicationsmodules. In some implementations, one or more of the arbitration methodsand/or schemes described herein (e.g., as discussed above with respectto FIG. 15A) are utilized to manage operations between communicationsmodules, radios, and/or antennas. In some implementations, one or moreof the co-existence methods and/or circuits described herein (e.g., asdiscussed above with respect to FIG. 16) are utilized to manageoperations between communications modules, radios, and/or antennas. Insome implementations, camera device 2600 includes an antenna coupled tomultiple communications modules. In some implementations, camera device2600 includes multiple antennas coupled to a single communicationsmodule (e.g., wireless communications module 2632).

In some implementations, a communications module is located in at leastone of regions 2623, 2633, and 2635 (FIG. 26D). In some implementations,a communications module is located in region 2647 (FIG. 26E). In someimplementations, a communications module is located in region 2645 (FIG.26G). In some implementations, a communications module is located inregion 2649 (FIG. 26J). In some implementations, a communications moduleis located at another position within camera device 2600. For example,camera device 2600 includes a first antenna (e.g., external antenna 2606in FIG. 26A) coupled to a first communications module (e.g., wirelesscommunications module 2632 in FIG. 26G) and a second antenna, such asadhesive antenna (e.g., located in region 2637 in FIG. 26D), coupled toa second communications module (e.g., located in region 2635 in FIG.26D). As another example, camera device 2600 includes a first antenna(e.g., external antenna 2606 in FIG. 26A) coupled to a firstcommunications module (e.g., wireless communications module 2632 in FIG.26G) and a second antenna, such as a chip antenna (e.g., located inregion 2623 in FIG. 26D), coupled to a second communications module(e.g., located in region 2645 in FIG. 26G).

In some implementations, camera device 2600 includes a communicationscontroller for managing communications via multiple antennas and/ormultiple radios. In some implementations, the communications controllercomprises a communications module (e.g., communications module 942 inFIG. 14). In some implementations, the communications controller islocated in region 2623 (FIG. 26F). In some implementations, thecommunications controller is located in region 2645 (FIG. 26G). In someimplementations, the communications controller is located in region 2647(FIG. 26I). In some implementations, a communications controller islocated at another position within camera device 2600. For example,camera device 2600 includes: (1) a first antenna (e.g., external antenna2606 in FIG. 26A) coupled to a first communications module (e.g.,wireless communications module 2632 in FIG. 26G); (2) a second antenna,such as a chip antenna (e.g., located in region 2623 in FIG. 26F),coupled to a second communications module (e.g., located in region 2645in FIG. 26G); and (3) a communications controller (e.g., located inregion 2647 in FIG. 26I).

FIGS. 27A-27I illustrate various assembly views of a camera device, inaccordance with some implementations. FIG. 27A shows an exterior view ofcamera device 2700 including casing 2701, lens 2702, motion sensor 2708,sensors 2706, microphone 2710, siren 2704, and stand 2703. In someimplementations, casing 2701 comprises a plastic casing. In someimplementations, stand 2703 comprises a metal stand. In someimplementations, stand 2703 comprises a plastic stand. In someimplementations, camera device 2700 includes one or more LEDs. In someimplementations camera device 2700 includes one or more IR LEDs. In someimplementations, camera device 2700 includes one or more speakers. Insome implementations, siren 2704 is used to send alerts to nearbypersons. In some implementations, sensors 2706 include one or more of: alight sensor, a humidity sensor, and a temperature sensor. In someimplementations, camera device 2700 switches between color mode andinfrared mode based on output from sensors 2706. In someimplementations, LEDs are utilized to provide illumination when cameradevice 2700 is in infrared mode. In some implementations, microphone2710 is utilized to detect noise above a predefined threshold. In someimplementations, microphone 2710 is utilized to receive voice commands.In some implementations, camera device 2700 includes one or moreexternal antennas.

FIG. 27B shows an exterior view of a side of camera device 2700including casing 2701, lens 2702, motion sensor 2708, and stand 2703.FIG. 27B also shows region 2705 on casing 2701. In some implementations,camera device 2700 includes one or more external antennas (e.g.,external antenna 2402, FIG. 24A). In some implementations, an externalantenna is located in region 2705. In some implementations, an externalantenna is located at another position on camera device 2700. In someimplementations, the one or more external antennas are utilized with oneor more of a variety of custom or standard wireless protocols (e.g.,IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart,ISA100.11a, WirelessHART, MiWi, etc.).

FIGS. 27C and 27D show additional exterior views of camera device 2700.FIG. 27C shows an exterior view of the back of camera device 2700including casing 2701, siren 2704, speaker 2714, reset affordance 2712,and stand 2703. In some implementations, reset affordance 2712 isutilized to reset camera device 2700 to a known state. FIG. 27D shows anexterior view of the back of camera device 2700 with stand 2703 removed.In FIG. 27D camera device 2700 includes casing 2701, siren 2704, speaker2714, reset affordance 2712, battery compartment 2716, and power port2718. In some implementations, battery compartment 2716 is utilized tocouple batteries to provide power to camera device 2700.

FIG. 27E shows an interior view of camera device 2700 including casing2701, circuit board 2720, siren 2704, and speaker 2714. Circuit board2720 includes reset button 2726, antenna 2722, and wirelesscommunications module 2707. In some implementations, wirelesscommunications module 2707 comprises a wireless communications chipmounted on board 2720. In some implementations, antenna 2722 comprises achip antenna (e.g., antenna 2422 in FIG. 24D). In some implementations,antenna 2722 comprises a silicon chip antenna. In some implementations,antenna 2722 is utilized with Wi-Fi and/or Bluetooth wirelesscommunications. In some implementations, antenna 2722 is utilized with15.4 wireless communications. In some implementations, an externalantenna (e.g., an external antenna located in region 2705 in FIG. 27D)is utilized for 15.4 wireless communications and antenna 2722 isutilized with Wi-Fi communications. In some implementations, an externalantenna is utilized for Bluetooth communications and antenna 2722 usedfor Wi-Fi communications.

FIG. 27E also shows regions 2709, 2711, 2713, 2715, 2717, and 2719 oncasing 2701, and 2721 on circuit board 2720. In some implementations,camera device 2700 includes one or more internal antennas in addition toantenna 2722. In some implementations, the one or more additionalinternal antennas include a sheet metal antenna (e.g., antenna 2404 inFIG. 24B). In some implementations, the one or more internal antennasinclude a board antenna (e.g., antenna 2414 in FIG. 24C). In someimplementations, the one or more internal antennas include a chipantenna (e.g., antenna 2422 in FIG. 24D). In some implementations, theone or more internal antennas include an adhesive antenna (e.g., antenna1104-1 in FIG. 11D).

In some implementations, an internal antenna, such as an adhesiveantenna, is located in region 2709. In some implementations, an internalantenna, such as an adhesive antenna, is located in at least one ofregions 2711, 2713, 2715, 2717, and 2719. In some implementations, aninternal antenna, such as a board antenna, is located in region 2721. Insome implementations, an internal antenna is located at another positionwithin camera device 2700. In some implementations, the one or moreadditional internal antennas are utilized with one or more of a varietyof custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi,ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a,WirelessHART, MiWi, etc.). In some implementations, an additionalinternal antenna is utilized for 15.4 wireless communications andantenna 2722 is utilized for Wi-Fi communications. In someimplementations, wireless communications module 2707 utilizes antenna2722 for wireless communication (e.g., Wi-Fi communications).

FIG. 27F shows a first side of circuit board 2720. The first side ofcircuit board 2720 includes antenna 2722, wireless communications module2707, and power port 2718, and reset button 2726. FIG. 27F also showsregion 2721. In some implementations, an internal antenna, such as achip antenna or a board antenna, is located in region 2721. In someimplementations, an internal antenna is located at another location oncircuit board 2720.

FIG. 27G shows a second side of circuit board 2720. The second side ofcircuit board 2720 includes memory 2731 and image sensor 2708. In someimplementations, image sensor 2708 is coupled to lens 2702 (FIG. 27A).In some implementations, memory 2731 comprises NAND memory. In someimplementations, memory 2731 comprises flash memory. FIG. 27G also showsregions 2723, 2725, 2727, and 2729. In some implementations, an internalantenna, such as a sheet metal antenna or a board antenna, is located inat least one of regions 2723, 2725, 2727, and 2729. In someimplementations, an internal antenna is located at another location oncircuit board 2720. In some implementations, the internal antenna isutilized with one or more of a variety of custom or standard wirelessprotocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave,Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.).

FIGS. 27H-27I shows interior views of camera device 2700 includingcasing 2701, circuit board 2730, and lens 2702. In some implementations,circuit board 2730 includes motion sensor 2708 (FIG. 27A). In someimplementations, an internal antenna is located on circuit board 2730(e.g., in region 2715). FIGS. 27H-27I also show regions 2713, 2717,2721, and 2733 on casing 2701. In some implementations, an internalantenna, such as an adhesive antenna, is located in at least one ofregions 2713, 2717, 2721, and 2733. In some implementations, an internalantenna, such as a chip antenna, is located in region 2715. In someimplementations, an internal antenna is located at another positionwithin camera device 2700. In some implementations, the internal antennais utilized with one or more of a variety of custom or standard wirelessprotocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave,Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.). In someimplementations, an internal antenna at one of these locations isutilized for Bluetooth wireless communications and antenna 2722 (FIG.27F) is utilized for Wi-Fi communications. In some implementations, aninternal antenna at one of these locations is utilized for 15.4 wirelesscommunications and antenna 2722 (FIG. 27F) is utilized for Wi-Ficommunications.

In some implementations, camera device 2700 includes multiple antennasand each antenna is coupled to a distinct communications module. Forexample, antenna 2722 is coupled to a first communications module foruse with Wi-Fi communications and an external antenna is coupled to asecond communications module for use with Bluetooth communications. Insome implementations, the camera device 2700 includes a controllermodule to manage operations of the first and second communicationsmodules. In some implementations, one or more of the arbitration methodsand/or schemes described herein (e.g., as discussed above with respectto FIG. 15A) are utilized to manage operations between communicationsmodules, radios, and/or antennas. In some implementations, one or moreof the co-existence methods and/or circuits described herein (e.g., asdiscussed above with respect to FIG. 16) are utilized to manageoperations between communications modules, radios, and/or antennas. Insome implementations, camera device 2700 includes an antenna coupled tomultiple communications modules. In some implementations, camera device2700 includes multiple antennas coupled to a single communicationsmodule (e.g., wireless communications module 2707).

In some implementations, a communications module is located in region2721 (FIG. 27E). In some implementations, a communications module islocated in at least one of regions 2723, 2725, 2727, and 2729 (FIG.27G). In some implementations, a communications module is located inregion 2715 (FIG. 27H). In some implementations, a communications moduleis located at another position within camera device 2700. For example,camera device 2700 includes a first antenna (e.g., antenna 2722 in FIG.27F) coupled to a first communications module (e.g., wirelesscommunications module 2707 in FIG. 27F) and a second antenna, such asadhesive antenna (e.g., located in region 2709 in FIG. 27E), coupled toa second communications module (e.g., located in region 2721 in FIG.27E). As another example, camera device 2700 includes a first antenna(e.g., antenna 2722 in FIG. 27F) coupled to a first communicationsmodule (e.g., wireless communications module 2707 in FIG. 27F) and asecond antenna, such as a chip antenna (e.g., located in region 2723 inFIG. 27G), coupled to a second communications module (e.g., located inregion 2725 in FIG. 27G).

In some implementations, camera device 2700 includes a communicationscontroller for managing communications via multiple antennas and/ormultiple radios. In some implementations, the communications controllercomprises a communications module (e.g., communications module 942 inFIG. 14). In some implementations, the communications controller islocated in region 2721 (FIG. 27F). In some implementations, thecommunications controller is located in at least one of regions 2723,2725, 2727, and 2728 (FIG. 27G). In some implementations, thecommunications controller is located in region 2715 (FIG. 27H). In someimplementations, a communications controller is located at anotherposition within camera device 2700. For example, camera device 2700includes: (1) a first antenna (e.g., antenna 2722 in FIG. 27F) coupledto a first communications module (e.g., wireless communications module2707 in FIG. 27F); (2) a second antenna, such as a chip antenna (e.g.,located in region 2715 in FIG. 27H), coupled to a second communicationsmodule (e.g., located in region 2727 in FIG. 27G); and (3) acommunications controller (e.g., located in region 2729 in FIG. 27G).

FIGS. 28A-28N illustrate various assembly views of a camera device, inaccordance with some implementations. FIG. 28A shows an exterior view ofcamera device 2800 including casing 2801, casing 2803, casing 2805, lens2808, LEDs 2806, light sensor 2804, speaker 2802, and microphone 2810.In some implementations, at least one of casings 2801, 2803, and 2805comprise a plastic casing. In some implementations, camera device 2800includes one or more additional sensors, such as a motion sensor, ahumidity sensor, and a temperature sensor. In some implementations,camera device 2800 switches between color mode and infrared mode basedon output from light sensor 2804. In some implementations, LEDs 2806 areutilized to provide illumination when camera device 2800 is in infraredmode. In some implementations, microphone 2810 is utilized to detectnoise above a predefined threshold. In some implementations, microphone2810 is utilized to receive voice commands.

FIG. 28A also shows regions 2807 and 2809 on casing 2801. In someimplementations, camera device 2800 includes one or more externalantennas (e.g., external antenna 2402, FIG. 24A). In someimplementations, an external antenna is located in region 2807. In someimplementations, an external antenna is located in region 2809. In someimplementations, an external antenna is located at another position oncamera device 2800.

FIG. 28B shows an exterior view of camera device 2811 including casing2813, casing 2815, casing 2817, lens 2816, LEDs 2814, light sensor 2812,and microphone 2818. In some implementations, camera device 2811includes one or more of the components of camera device 2800. In someimplementations, the functionality of camera device 2811 includes all ofthe functionality of camera device 2800. In some implementations, cameradevice 2811 includes one or more speakers. In some implementations,camera device 2811 includes one or more additional sensors, such as amotion sensor, a humidity sensor, and a temperature sensor. In someimplementations, camera device 2811 switches between color mode andinfrared mode based on output from light sensor 2812. In someimplementations, LEDs 2814 are utilized to provide illumination whencamera device 2811 is in infrared mode. In some implementations,microphone 2818 is utilized to detect noise above a predefinedthreshold. In some implementations, microphone 2818 is utilized toreceive voice commands. In some implementations, camera device 2811includes one or more external antennas.

FIG. 28C shows a mount for use with camera device 2800 or camera device2811. Mount 2820 includes adjustor 2822 for adjusting the orientation ofan attached camera device. In some implementations, mount 2820 comprisesa plastic mount. In some implementations, mount 2820 comprises a metalmount.

FIG. 28D shows an additional exterior view of camera device 2800. FIG.28B shows an exterior view of the back of camera device 2800 includingcasing 2801, casing 2803, casing 2805, power port 2816, communicationsport 2814, antenna port 2812, and audio ports 2818. In someimplementations, communications port 2814 is an Ethernet port. Antennaport 2812 is utilized to couple an external antenna (e.g., externalantenna 2402, FIG. 24A) to camera device 2800. In some implementations,antenna port 2812 and an external antenna are utilized with one or moreof a variety of custom or standard wireless protocols (e.g., IEEE802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart,ISA100.11a, WirelessHART, MiWi, etc.). In some implementations, antennaport 2812 and an external antenna are utilized with Wi-Fi and/orBluetooth wireless communications. In some implementations, antenna port2812 and an external antenna are utilized with 15.4 wirelesscommunications. In some implementations, an internal antenna is utilizedfor 15.4 wireless communications and antenna port 2812 and an externalantenna are utilized with Wi-Fi communications. In some implementations,an internal antenna is utilized for Bluetooth communications and antennaport 2812 and an external antenna are used for Wi-Fi communications.

FIG. 28D also shows regions 2807 and 2809 on casing 2801, region 2819 oncasing 2803, and region 2821 on casing 2805. In some implementations,camera device 2800 includes one or more additional external antennas(e.g., external antenna 2402, FIG. 24A) in addition to an externalantenna coupled to antenna port 2812. In some implementations, anexternal antenna is located in at least one of regions 2807, 2809, 2819,and 2821. For example, an antenna port similar in design to antenna port2812 is located in region 2821 and an external antenna is coupled toeach antenna port. In some implementations, antenna port 2812 and anexternal antenna utilized for communications at a first wavelength andthe one or more additional external antennas are utilized forcommunications at one or more wavelengths distinct from the firstwavelength. For example, the additional external antenna is utilized for15.4 wireless communications and an external antenna coupled to antennaport 2812 is utilized for Wi-Fi communications. In some implementations,an external antenna is located at another position on camera device2800.

FIG. 28E shows an internal view of camera device 2800. FIG. 28E showscasing 2801 de-coupled from casing 2805. FIG. 28E also shows gear 2830for rotating the point of view of camera device 2800 in conjunction witha motor.

FIG. 28F shows an internal view of camera device 2800. FIG. 28F showsthe interior of casing 2805. FIG. 28F also shows antenna port 2812,circuit board 2836, and microphone 2823. Circuit board 2836 includesmemory 2832 (e.g., SRAM) and processor 2834 (e.g., ARM microcontroller).FIG. 28F also shows regions 2825, 2827, 2829, 2831, 2833, 2835, and 2837on casing 2805, regions 2839, 2841, and 2843 on circuit board 2836. Insome implementations, camera device 2800 includes one or more internalantennas. In some implementations, the one or more internal antennasinclude a sheet metal antenna (e.g., antenna 2404 in FIG. 24B). In someimplementations, the one or more internal antennas include a boardantenna (e.g., antenna 2414 in FIG. 24C). In some implementations, theone or more internal antennas include a chip antenna (e.g., antenna 2422in FIG. 24D). In some implementations, the one or more internal antennasinclude an adhesive antenna (e.g., antenna 1104-1 in FIG. 11D).

In some implementations, an internal antenna, such as an adhesiveantenna, is located in region 2825. In some implementations, an internalantenna, such as an adhesive antenna, is located in at least one ofregions 2827, 2829, 2831, 2833, 2835, and 2837. In some implementations,an internal antenna, such as a chip antenna, is located in region 2839.In some implementations, an internal antenna, such as a board antenna,is located in region 2841. In some implementations, an internal antenna,such as a sheet metal antenna, is located in region 2843. In someimplementations, an internal antenna is located at another position oncircuit board 2836. In some implementations, an internal antenna islocated at another position within camera device 2800. In someimplementations, the internal antenna is utilized with one or more of avariety of custom or standard wireless protocols (e.g., IEEE 802.15.4,Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a,WirelessHART, MiWi, etc.). In some implementations, the internal antennais utilized for 15.4 wireless communications and an external antennacoupled to antenna port 2812 is utilized for Wi-Fi communications.

FIG. 28G shows a first side of circuit board 2836. The first side ofcircuit board 2836 includes memory 2832 and processor 2834. FIG. 28Galso shows regions 2839, 2841, and 2843. In some implementations, aninternal antenna, such as a chip antenna or a board antenna, is locatedin at least one of regions 2839, 2841, and 2843. In someimplementations, an internal antenna is located at another location oncircuit board 2836.

FIG. 28H shows a second side of circuit board 2836. The second side ofcircuit board 2836 includes audio ports 2818, communications port 2814,power port 2816, and LED 2846. In some implementations, LED 2846 isutilized to indicate a status of camera device 2800. FIG. 28H also showscircuit board 2842 mounted on circuit board 2836. Circuit board 2842includes wireless communications module 2838 and antenna connector 2844for coupling communications module 2838 to an external antenna coupledto antenna port 2812 (FIG. 28F). In some implementations, wirelesscommunications module 2838 utilizes an external antenna coupled toantenna port 2812 (FIG. 28F) for wireless communication (e.g., Wi-Ficommunications).

FIG. 28H also shows regions 2845 and 2847. In some implementations, aninternal antenna, such as a sheet metal antenna, is located in region2845. In some implementations, an internal antenna, such as a chipantenna, is located in region 2847. In some implementations, an internalantenna is located at another location on circuit board 2836.

FIG. 28I shows circuit board 2842 including wireless communicationsmodule 2838 and antenna connector 2844. In some implementations,wireless communications module 2838, via antenna connector 2844,utilizes an external antenna coupled to antenna port 2812 (FIG. 28F) forwireless communication (e.g., Bluetooth communications).

FIGS. 28J-28K show interior views of camera device 2800 where a portionof casing 2803 is de-coupled from casing 2801. FIG. 28J also shows motor2848 for rotating the point of view of camera device 2800 in conjunctionwith one or more gears. FIGS. 28J-29K also show circuit board 2846mounted within casing 2803. In some implementations, circuit board 2846includes an image sensor coupled to lens 2808 (FIG. 28A). In someimplementations, circuit board 2846 is coupled to LEDs 2806 (FIG. 28A).FIGS. 28J-28K also show regions 2807 and 2809. In some implementations,camera device 2800 includes one or more external antennas located withinregion 2807 and or 2809.

FIG. 28L shows a first side of circuit board 2846. The first side ofcircuit board 2846 includes sensor controller 2847. FIG. 28M shows asecond side of circuit board 2846. The second side of circuit board 2846includes image sensor 2850. In some implementations, image sensor 2850is coupled to lens 2808 (FIG. 28A) and sensor controller 2847 (FIG.28L). FIG. 28M also shows regions 2849, 2851, and 2853 on circuit board2846. In some implementations, an internal antenna, such as a sheetmetal antenna, is located in region 2849. In some implementations, aninternal antenna, such as a chip antenna, is located in region 2851. Insome implementations, an internal antenna, such as a board antenna, islocated in region 2853. In some implementations, an internal antenna islocated at another location on circuit board 2846.

FIG. 28N shows lens 2834 coupled to board 2846 (e.g., coupled to imagesensor 2850 of circuit board 2846). FIG. 28N also shows LEDs 2806mounted on circuit board 2852 and circuit board 2852 coupled to circuitboard 2846.

In some implementations, camera device 2800 (and/or camera device 2811)includes multiple antennas and each antenna is coupled to a distinctcommunications module. For example, an external antenna is coupled to afirst communications module via antenna port 2812 for use with Wi-Ficommunications and an internal antenna is coupled to a secondcommunications module for use with Bluetooth communications. In someimplementations, the camera device 2800 includes a controller module tomanage operations of the first and second communications modules. Insome implementations, one or more of the arbitration methods and/orschemes described herein (e.g., as discussed above with respect to FIG.15A) are utilized to manage operations between communications modules,radios, and/or antennas. In some implementations, one or more of theco-existence methods and/or circuits described herein (e.g., asdiscussed above with respect to FIG. 16) are utilized to manageoperations between communications modules, radios, and/or antennas. Insome implementations, camera device 2800 includes an antenna coupled tomultiple communications modules. In some implementations, camera device2800 includes multiple antennas coupled to a single communicationsmodule (e.g., wireless communications module 2838, FIG. 28H).

In some implementations, a communications module is located in at leastone of regions 2839, 2841, and 2843 (FIG. 28F). In some implementations,a communications module is located in at least one of regions 2845 and2847 (FIG. 28H). In some implementations, a communications module islocated at another position on circuit board 2836. In someimplementations, a communications module is located in at least one ofregions 2849, 2851, and 2853 (FIG. 28M). In some implementations, acommunications module is located at another position on circuit board2846. In some implementations, a communications module is located atanother position within camera device 2800. For example, camera device2800 includes a first antenna (e.g., an exterior antenna coupled toantenna port 2812 in FIG. 28F) coupled to a first communications module(e.g., wireless communications module 2838, FIG. 28H) and a secondantenna, such as adhesive antenna (e.g., located in region 2825 in FIG.28F), coupled to a second communications module (e.g., located in region2841 in FIG. 28F). As another example, camera device 2800 includes afirst antenna (e.g., an exterior antenna coupled to antenna port 2812 inFIG. 28F) coupled to a first communications module (e.g., wirelesscommunications module 2838, FIG. 28H) and a second antenna, such as achip antenna (e.g., located in region 2851 in FIG. 28M), coupled to asecond communications module (e.g., located in region 2853 in FIG. 28M).

In some implementations, camera device 2800 (and/or camera device 2811)includes a communications controller for managing communications viamultiple antennas and/or multiple radios. In some implementations, thecommunications controller comprises a communications module (e.g.,communications module 942 in FIG. 14). In some implementations, thecommunications controller is located in at least one of regions 2839,2841, and 2843 (FIG. 28F). In some implementations, the communicationscontroller is located in at least one of regions 2845 and 2847 (FIG.28H). In some implementations, a communications controller is located atanother position on circuit board 2836. In some implementations, acommunications controller is located in at least one of regions 2849,2851, and 2853 (FIG. 28M). In some implementations, a communicationscontroller is located at another position on circuit board 2846. In someimplementations, a communications controller is located at anotherposition within camera device 2800. For example, camera device 2800includes: (1) a first antenna (e.g., an exterior antenna coupled toantenna port 2812 in FIG. 28F) coupled to a first communications module(e.g., wireless communications module 2838, FIG. 28H); (2) a secondantenna, such as a chip antenna (e.g., located in region 2843 in FIG.28F), coupled to a second communications module (e.g., located in region2839 in FIG. 28F); and (3) a communications controller (e.g., located inregion 2841 in FIG. 28F).

FIGS. 29A-29I illustrate various assembly views of a camera device, inaccordance with some implementations. FIG. 29A shows an exterior view ofcamera device 2900 including casing 2901, lens 2906, LED 2904, sensor2908, microphone 2902, and stand 2910. In some implementations, casing2901 comprises a plastic casing. In some implementations, stand 2910comprises a metal stand. In some implementations, sensor 2908 comprisesa motion sensor. In some implementations, sensor 2908 comprises a lightsensor. In some implementations, camera device 2900 includes one or moreadditional sensors, such as a motion sensor, a humidity sensor, and atemperature sensor. In some implementations, camera device 2900 switchesbetween color mode and infrared mode based on output from sensor 2908.In some implementations, LED 2904 is utilized to convey a status ofcamera device 2900 to nearby persons. In some implementations, cameradevice 2900 includes a plurality of LEDs (e.g., around lens 2906). Insome implementations, the plurality of LEDs provides illumination whencamera device 2900 is in infrared mode. In some implementations,microphone 2902 is utilized to detect noise above a predefinedthreshold. In some implementations, microphone 2902 is utilized toreceive voice commands.

FIG. 29B shows another exterior view of camera device 2900. FIG. 29Bshows camera device 2900 including casing 2901, lens 2906, LED 2904,sensor 2908, microphone 2902, and stand 2910. In FIG. 29B casing 2901 israised up from stand 2910, while in FIG. 29A casing 2901 is nestingwithin stand 2910.

FIG. 29C shows another exterior view of camera device 2900. FIG. 29Cshows the back of camera device 2900 including setup affordance 2912,speaker 2914, and communications port 2916. In some implementations,communications port 2916 comprises a micro-USB port. In someimplementations, setup affordance 2912 is utilized to wirelessly couplecamera device 2900 to one or more other electronic devices. In someimplementations, setup affordance 2912 is utilized to set camera device2900 to a known state.

FIG. 29D shows an interior view of camera device 2900 including casing2901, circuit board 2920, and speaker 2914. Circuit board 2920 includessetup affordance 2912 and memory 2921. In some implementations, memory2921 comprises flash memory.

FIG. 29D also shows regions 2903, 2905, and 2907 on casing 2901. In someimplementations, camera device 2900 includes one or more internalantennas. In some implementations, the one or more internal antennasinclude an adhesive antenna (e.g., antenna 1104-1 in FIG. 11D). In someimplementations, an internal antenna, such as an adhesive antenna, islocated in at least one of regions 2903, 2905, 2907. In someimplementations, an internal antenna is located at another positionwithin camera device 2900. In some implementations, the one or moreinternal antennas are utilized with one or more of a variety of customor standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee,6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART,MiWi, etc.).

FIG. 29E shows a first side of circuit board 2920. The first side ofcircuit board 2920 includes memory 2921 setup affordance 2912, speakerconnectors 2940, and microphone connectors 2942. FIG. 29F shows a secondside of circuit board 2920. The second side of circuit board 2920includes processor 2923.

FIG. 29G shows lens 2906, circuit board 2926, and circuit board 2928.Circuit board 2928 includes LEDs 2930 and LED 2904. In someimplementations, LEDs 2930 comprise a plurality of infrared (IR) LEDs.In some implementations, lens 2906 is mounted to circuit board 2926. Insome implementations, antenna connector 2932 is coupled to circuit board2926.

FIG. 29H shows circuit board 2926 including wireless communicationmodule 2936 and antenna connector 2932. In some implementations,wireless communication module 2936 comprises a wireless communicationchip. In some implementations, wireless communications module 2936utilizes an antenna for wireless communication (e.g., Wi-Ficommunications). In some implementations, wireless communication module2936 is utilized with one or more of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.).

FIG. 29H also shows regions 2933, 2935, and 2937 on circuit board 2926.In some implementations, camera device 2900 includes one or moreinternal antennas. In some implementations, the one or more internalantennas include a sheet metal antenna (e.g., antenna 2404 in FIG. 24B).In some implementations, the one or more internal antennas include aboard antenna (e.g., antenna 2414 in FIG. 24C). In some implementations,the one or more internal antennas include a chip antenna (e.g., antenna2422 in FIG. 24D).

In some implementations, an internal antenna, such as a chip antenna, islocated in region 2933. In some implementations, an internal antenna,such as a board antenna, is located in region 2935. In someimplementations, an internal antenna, such as a sheet metal antenna, islocated in region 2937. In some implementations, an internal antenna islocated at another position on circuit board 2926. In someimplementations, the one or more internal antennas are utilized with oneor more of a variety of custom or standard wireless protocols (e.g.,IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart,ISA100.11a, WirelessHART, MiWi, etc.). In some implementations, a firstinternal antenna is utilized for 15.4 wireless communications and asecond internal antenna is utilized for Wi-Fi communications.

FIG. 29I shows an interior view of camera device 2900. FIG. 29I showscasing 2901 with antenna 2946. In some implementations, antenna 2946comprises an adhesive antenna (e.g., antenna 1104-1 in FIG. 11D). Insome implementations, antenna 2946 is utilized with Wi-Fi and/orBluetooth wireless communications. In some implementations, antenna 2946is utilized with 15.4 wireless communications. In some implementations,antenna 2946 is coupled to wireless communication module 2936 viaantenna connector 2932. In some implementations, another internalantenna (e.g., an adhesive antenna located in region 2905 in FIG. 29D)is utilized for 15.4 wireless communications and antenna 2946 isutilized with Wi-Fi communications. In some implementations, anadditional internal antenna is utilized for Bluetooth communications andantenna 2946 used for Wi-Fi communications.

FIG. 29I also shows regions 2947 and 2949 on casing 2901. In someimplementations, camera device 2900 includes one or more internalantennas in addition to antenna 2946. In some implementations, the oneor more additional internal antennas include an adhesive antenna (e.g.,antenna 1104-1 in FIG. 11D). In some implementations, an internalantenna, such as an adhesive antenna, is located in at least one ofregions 2947 and 2949. In some implementations, an internal antenna islocated at another position within camera device 2900. In someimplementations, the one or more additional internal antennas areutilized with one or more of a variety of custom or standard wirelessprotocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave,Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.). For example,antenna 2946 is utilized with Wi-Fi communications and a second internalantenna (e.g., located in region 2949) is utilized with 15.4communications.

In some implementations, camera device 2900 includes multiple antennasand each antenna is coupled to a distinct communications module. Forexample, antenna 2932 is coupled to a first communications module foruse with Wi-Fi communications and a second internal antenna is coupledto a second communications module for use with Bluetooth communications.In some implementations, the camera device 2900 includes a controllermodule to manage operations of the first and second communicationsmodules. In some implementations, one or more of the arbitration methodsand/or schemes described herein (e.g., as discussed above with respectto FIG. 15A) are utilized to manage operations between communicationsmodules, radios, and/or antennas. In some implementations, one or moreof the co-existence methods and/or circuits described herein (e.g., asdiscussed above with respect to FIG. 16) are utilized to manageoperations between communications modules, radios, and/or antennas. Insome implementations, camera device 2900 includes an antenna coupled tomultiple communications modules. In some implementations, camera device2900 includes multiple antennas coupled to a single communicationsmodule (e.g., wireless communications module 2936). For example, antenna2946 and a second antenna (e.g., an adhesive antenna located in region2947 of FIG. 29I) are both coupled to wireless communications module2936 (FIG. 29H).

In some implementations, a communications module is located in at leastone of regions 2933, 2935, and 2937 of circuit board 2926 (FIG. 29H). Insome implementations, a communications module is located at anotherlocation on circuit board 2926. In some implementations, acommunications module is located at another position within cameradevice 2900. For example, camera device 2900 includes a first antenna(e.g., antenna 2946 in FIG. 29I) coupled to a first communicationsmodule (e.g., wireless communications module 2936 in FIG. 29H) and asecond antenna, such as adhesive antenna (e.g., located in region 2903in FIG. 29D), coupled to a second communications module (e.g., locatedin region 2933 in FIG. 29H). As another example, camera device 2900includes a first antenna (e.g., antenna 2946 in FIG. 29I) coupled to afirst communications module (e.g., wireless communications module 2936in FIG. 29H) and a second antenna, such as a chip antenna (e.g., locatedin region 2933 in FIG. 29H), coupled to a second communications module(e.g., located in region 2937 in FIG. 29H).

In some implementations, camera device 2900 includes a communicationscontroller for managing communications via multiple antennas and/ormultiple radios. In some implementations, the communications controllercomprises a communications module (e.g., communications module 942 inFIG. 14). In some implementations, the communications controller islocated in at least one of regions 2933, 2935, and 2937 (FIG. 29H). Insome implementations, a communications controller is located at anotherposition within camera device 2900. For example, camera device 2900includes: (1) a first antenna (e.g., antenna 2946 in FIG. 29I) coupledto a first communications module (e.g., wireless communications module2936 in FIG. 29H); (2) a second antenna, such as an adhesive antenna(e.g., located in region 2947 in FIG. 29I), coupled to a secondcommunications module (e.g., located in region 2937 in FIG. 29H); and(3) a communications controller (e.g., located in region 2933 in FIG.29H).

For situations in which the systems discussed above collect informationabout users, the users may be provided with an opportunity to opt in/outof programs or features that may collect personal information (e.g.,information about a user's preferences or usage of a smart device). Inaddition, in some implementations, certain data may be anonymized in oneor more ways before it is stored or used, so that personallyidentifiable information is removed. For example, a user's identity maybe anonymized so that the personally identifiable information cannot bedetermined for or associated with the user, and so that user preferencesor user interactions are generalized (for example, generalized based onuser demographics) rather than associated with a particular user.

Although some of various drawings illustrate a number of logical stagesin a particular order, stages that are not order dependent may bereordered and other stages may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beobvious to those of ordinary skill in the art, so the ordering andgroupings presented herein are not an exhaustive list of alternatives.Moreover, it should be recognized that the stages could be implementedin hardware, firmware, software or any combination thereof.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first type ofsignal could be termed a second type of signal, and, similarly, a secondtype of signal could be termed a first type of signal, without departingfrom the scope of the various described implementations. The first typeof signal and the second type of signal are both types of signals, butthey are not the same type of signal.

The terminology used in the description of the various describedimplementations herein is for the purpose of describing particularimplementations only and is not intended to be limiting. As used in thedescription of the various described implementations and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting”or “in accordance with a determination that,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event]” or “in accordance with a determination that [astated condition or event] is detected,” depending on the context.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit the scope of the claims to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The implementations were chosen in order to best explain theprinciples underlying the claims and their practical applications, tothereby enable others skilled in the art to best use the implementationswith various modifications as are suited to the particular usescontemplated.

What is claimed is:
 1. A camera assembly, comprising: an enclosedhousing having a rear surface, a front surface, and a periphery; a lensmodule located within the housing and configured to receive light viathe front surface; a circuit board comprising communication circuitrylocated within the housing and configured to wirelessly communicate overa plurality of different communication protocols; a first antennaarranged at a location on the circuit board, the first antennaconfigured for communication over a first one of the communicationprotocols; and a second antenna arranged at a location on the innersurface of the periphery, the second antenna configured forcommunication over a second one of the communication protocols.
 2. Thecamera assembly of claim 1, wherein the second antenna is arranged atthe location on the inner surface of the periphery by an adhesivematerial.
 3. The camera assembly of claim 1, wherein the first antennaand the second antenna are configured to operate at the same frequency.4. The camera assembly of claim 1, wherein the first antenna and thesecond antenna are configured to operate at distinct frequencies.
 5. Thecamera assembly of claim 1, wherein the communication circuitry includesa first circuit configured for communication over the firstcommunication protocol and a second circuit configured for communicationover the second communication protocol, wherein the first circuit andthe second circuit are distinct.
 6. The camera assembly of claim 1,wherein the communication circuitry is an integrated circuit configuredfor communication over both the first and second communicationprotocols.
 7. The camera assembly of claim 1, wherein the communicationcircuitry is configured to wireless communicate over at least threedifferent communication protocols.
 8. The camera assembly of claim 7,wherein the second antenna is further configured for communication overa third one of the communication protocols.
 9. The camera assembly ofclaim 8, wherein: the first antenna is configured to transmit andreceive, over the first communication protocol, signals comprising oneor more of alerts, control signals and status information to and fromother smart home devices; and the second antenna is configured totransmit and receive, over the second communication protocol signals forconfiguring the smart home device, and over the third communicationprotocol data corresponding to video captured by the smart home device.10. The camera assembly of claim 1, wherein the communication circuitryis further configured to provide transmission access for communicatingover the first communication protocol while denying transmission accessfor communicating over the second communication protocol, whiledetecting an activated priority control signal.
 11. The camera assemblyof claim 1, wherein the first antenna has a first orientation and thesecond antenna has a second orientation such that the impact from thepresence and interference of each other antenna are suppressed.
 12. Thecamera assembly of claim 1, wherein the first antenna or the secondantenna is configured to transmit and receive wireless signals in awireless local area network according to the IEEE 802.11 specifications.13. The camera assembly of claim 1, wherein the first antenna or thesecond antenna is configured to transmit and receive wireless signals ina wireless personal area network according to the IEEE 802.15.4standard.
 14. The camera assembly of claim 1, wherein the first antennaor the second antenna is configured to transmit and receive wirelesssignals according to the Bluetooth Low Energy standard.
 15. The cameraassembly of claim 1, wherein the first antenna and the second antennaare electrically coupled to a duplex that controls their connections toa single wireless receiver circuit.
 16. The camera assembly of claim 1,wherein video data captured by the lens module is exchanged between thecamera assembly and a server using a wireless local area network.